helpSavannah Administration - Support: sr #107671, Viewing Job list of multiple...

 
 

sr #107671: Viewing Job list of multiple project types.

Submitted by:  shailesh <shailesh_ghadge>
Submitted on:  Sun 17 Apr 2011 11:03:52 AM UTC  
 
Category: Savannah websitePriority: 5 - Normal
Severity: 3 - NormalStatus: Done
Assigned to: NoneOperating System: GNU/Linux
Open/Closed: Closed

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Tue 20 Aug 2013 10:33:21 AM UTC, comment #26:

Closing the sr.

Pavel Kharitonov <ineiev>
Site Administrator
Sun 18 Aug 2013 03:56:46 PM UTC, comment #25:

What I did yesterday included an updated version of that patch.

Pavel Kharitonov <ineiev>
Site Administrator
Sat 17 Aug 2013 10:21:11 PM UTC, comment #24:

I think those are great improvements. Thanks for doing the work. (I wonder what the Sav! (sav.git) repository is.)

So, going back a step, how about your patch switching things to point to /p/administration now?

Thanks,
k

Karl Berry <karl>
Site Administrator
Sat 17 Aug 2013 12:48:25 PM UTC, comment #23:

So, I added a note on 'administration' main page how to get Savane; updated the URLs; rewrote frontend.sv.gnu.org:/etc/savane/content/gnu-content/git/index.txt to list multiple repositories.

I also added a cron job to frontend.sv.gnu.org:/etc/cron.d/sv_export to fetch the list of the repositores from vcs.sv.gnu.org to /etc/savane/cgitrepos, though I'm not sure those are the right places for that job and that file.

Pavel Kharitonov <ineiev>
Site Administrator
Fri 16 Aug 2013 03:05:05 PM UTC, comment #22:

> Can you work on that?


I'll try.

Pavel Kharitonov <ineiev>
Site Administrator
Thu 15 Aug 2013 09:26:45 PM UTC, comment #21:

> Then /p/administration should clearly say how to clone
> administration/savane.git.


I totally agree (regardless of anything else).

And for every package with multiple git repositories, it should show all the available repositories.

Can you work on that?

> pushing current
> administration/savane.git master as a new branch of
> administration.git


I'm afraid that doesn't make sense to me. But in any case, having multiple git repositories is a general "problem" ("feature"), so it would be nice to support it correctly.

?

k

Karl Berry <karl>
Site Administrator
Thu 15 Aug 2013 12:56:36 PM UTC, comment #20:

> how about changing the links to /p/administration?


Then /p/administration should clearly say how to clone administration/savane.git.

Since the natural way to get current source code for a Savannah group is to follow the links under "Development Tools", we might consider pushing current administration/savane.git master as a new branch of administration.git (e.g. "savane") --- and further maintaining the code there.

Pavel Kharitonov <ineiev>
Site Administrator
Wed 14 Aug 2013 09:45:38 PM UTC, comment #19:

> To be precise, there are at least two repositories,
> "administration.git" and "administration/savane.git"


Oh! It finally begins to become clear. And how is one supposed to know that, when https://savannah.gnu.org/git/?group=administration doesn't mention savane.git? Sigh. (This multiple repository per project stuff that git loves so much seems to me like a terrible idea for us. Creates so much confusion.)

Anyway, so then how about changing the links to /p/administration?

My main point is that it does not sound correct or maintainable to link to a specific git repository. Much better to link to a project. If no current projects suffice, we should make it so one does. (I seem to vaguely recall having this sam conversation with Sylvain years and years ago, and nothing coming of it. Sigh.)

It sounds like the administration project has everything that is interesting, and all the savane projects are the rewrites that have never come to fruition. Is that accurate?

Thanks,
Karl

Karl Berry <karl>
Site Administrator
Wed 14 Aug 2013 01:52:33 PM UTC, comment #18:

> Wouldn't it be better to just replace the links to .../projects/savane-cleanup with .../projects/savane,


https://savannah.nongnu.org/p/savane is a rewrite, it is not
used on Savannah yet; https://gna.org/p/savane is not what
Savannah uses, either, and https://gna.org/p/savane links to
https://savannah.gnu.org/p/savane-cleanup, which again is not
what Savannah actually uses. None of them TTBOMK links
to the authoritative sources for Savannah.

> Michael: do you know what the "administration" project's
> git repository is for? just documentation?


To be precise, there are at least two repositories,
"administration.git" and "administration/savane.git" :)

Pavel Kharitonov <ineiev>
Site Administrator
Tue 13 Aug 2013 03:54:26 PM UTC, comment #17:

Ineiev: Wouldn't it be better to just replace the links to .../projects/savane-cleanup with .../projects/savane, instead of specifically the git repository? More information, and there's no reason to suppose git will be the last or only word in source repositories.

Michael: do you know what the "administration" project's git repository is for? just documentation?

Thanks,
Karl

Karl Berry <karl>
Site Administrator
Mon 12 Aug 2013 04:52:34 PM UTC, comment #16:

> re the git push: what is the error you got?


I must apologize; in fact it works. I think I just was used to look at project's pages and find the instructions for CVS, and I didn't realized that it may be more complicated for Git.

>To be clear, the currently we're using http://git.savannah.gnu.org/cgit/administration/savane.git/ as the authoritative sources for savannah.


So, I attach a patch against this repository (frontend.diff) and a patch against `administration' web pages (savane-refs.diff) to fix the pointers (I didn't test them, especially I'm not sure about the change in content/gnu-content/page_footer.txt).

(file #28823, file #28824)

Pavel Kharitonov <ineiev>
Site Administrator
Mon 12 Aug 2013 01:40:18 AM UTC, comment #15:

To be clear, the currently we're using http://git.savannah.gnu.org/cgit/administration/savane.git/ as the authoritative sources for savannah.

Certain features, like comments in news articles, are disabled in that repository.

The savane-cleanup repository is not used in production anywhere that I know of.

Michael J. Flickinger <mjflick>
Site Administrator
Mon 12 Aug 2013 12:13:29 AM UTC, comment #14:

hi ineiev,

yes, so (under my theory) we would change the savannah source pointer (you mean just in the project?), not savane-cleanup. this wouldn't be "migrating" to anything new, just recognizing reality. does it make sense?

re the git push: what is the error you got? i'm confused. i certainly have no special information. i'm not sure i ever tried a git push there. probably not.

thanks,
k

Karl Berry <karl>
Site Administrator
Sun 11 Aug 2013 04:55:04 AM UTC, comment #13:

> Will anything bad come of pushing that?


There are two problems: first, few people know how to push it (I don't, what I tried didn't work), second, Savannah points to savane-cleanup as her source code.

> therefore there's no point in ever doing anything with savane-cleanup


Then we should take a different repository, migrate to it and
adjust the pointers.

> i mean, is the live system really running out of /usr/src/savane?


Yes. e.g. when I add some files, Savannah adds corresponding pages.

Pavel Kharitonov <ineiev>
Site Administrator
Sat 10 Aug 2013 11:03:35 PM UTC, comment #12:

i have not investigated the differences between the savane and savane-cleanup repos, but i have the impression they are substantial. as part of Sylvain's historical effort to merge gna and savannah sources, long since abandoned on both sides as far as i know.

i don't believe savane-cleanup is used as a live system checkout anywhere. do you know otherwise? not that it would surprise me if it were; i have never seen a comprehensible explanation of all the different savannah-related source repos (git, cvs, bzr, others, have all been/are being used) and where they are checked out and for what purpose, either. this is one of the biggest barriers to people (me, you, john, bob, anyone ...) actually working on savannah.

thus, barring other input, i confess i have a different view - my view is that we should recognize the reality that no one on either the gna or savannah side is going to finish a savane merge any time in the foreseeable future. therefore there's no point in ever doing anything with savane-cleanup, and it should be archived in the dust bin of history.

as for /usr/src/savane and the savane repo: certainly i agree things should be updated in the repository, but i don't know how to tell what has been changed or what might result from updates, so i'm always afraid to do anything. i mean, is the live system really running out of /usr/src/savane? that seems like a totally wrong directory choice for a live runtime to me.

anyway, i just moved frontend:/usr/src/savane/frontend/php/images/common/contexts1/people.orig.png.prev to /root/archive on frontend, to get it out of the hier, anyway. git status now reports "Your branch is ahead of 'origin/master' by 9 commits." as well as the modified people.orig.png. Will anything bad come of pushing that? Doesn't seem like it.

thanks,
karl

Karl Berry <karl>
Site Administrator
Sat 10 Aug 2013 04:21:00 AM UTC, comment #11:

To further clarify it: in June I actually committed
index.txt in /etc/savane/content/gnu-content/people,
it is a working copy of web pages of the `administration'
group.

Pavel Kharitonov <ineiev>
Site Administrator
Sat 10 Aug 2013 04:05:07 AM UTC, comment #10:

> git push still doesn't work


I meant that I couldn't push the changes to origin in
/usr/src/savane on frontend.gnu.org.

BTW, https://savannah.gnu.org says that its "Source Code" is [0],
whereas the code in /usr/src/savane/ on frontend.gnu.org
points to [1], which is a different repository.

I'd suggest to
(0) commit the uncommitted file,
frontend/php/images/common/contexts1/people.orig.png;
(1) push (probably to merge) the actual code to savanne-cleanup;
(2) checkout savane-cleanup master on frontend.gnu.org.

Of course it is easier to edit files directly on frontend without
pushing them anywhere, but it must confuse those users who are
curious to learn about how the bugs work.

(I really can't tell what reasons were to maintain
the working code in /administration/savane.git, I suggest
what seems the least surprising order to me.)

[0] http://git.sv.gnu.org/gitweb/?p=savane-cleanup.git;a=blob;f=frontend/php/index.php;hb=HEAD
[1] git://git.sv.gnu.org/administration/savane.git

Pavel Kharitonov <ineiev>
Site Administrator
Fri 09 Aug 2013 11:16:18 PM UTC, comment #9:

the original request is done, thanks to Ineiev. (https://savannah.gnu.org/people/ now allows selecting of multiple categories, etc.)

I left it open because of Ineiev's comment that:

> git push still doesn't work

[on frontend.sv.gnu.org, but I'm not sure of the directory involved, since /etc/savane/content/gnu-content/people is in CVS, not git. Unless you were doing git-over-CVS, Ineiev?]

k

Karl Berry <karl>
Site Administrator
Fri 09 Aug 2013 07:27:40 PM UTC, comment #8:

Is this still an issue? Can we close this?

John Schmidt <johnschmidt4>
Sun 02 Jun 2013 05:46:36 AM UTC, comment #7:

I've replaced it with the new version; I also git committed the changes on frontend.sv.gnu.org (git push still doesn't work there).

Pavel Kharitonov <ineiev>
Site Administrator
Sat 01 Jun 2013 11:01:30 PM UTC, comment #6:

looks just fine to me now, except there is a trivial typo: missing period after "visit the support manager". Which text actually should be a link (to https://savannah.gnu.org/support/?group=administration I guess).

Can you fix that and then make it live, please?

Thanks!!

Karl Berry <karl>
Site Administrator
Sat 01 Jun 2013 09:02:36 AM UTC, comment #5:

Next revision is online.

> ...if category name and project type were a link that brings up the jobs that are listed


Done.

> "Any" category which just brings up all jobs in the selected project types


Done (I think --- it shows all jobs available; all jobs in selected project types are shown when no category is selected).

> we could use that link on various web pages (help GNU/GNU todo/GNU tasks/etc.).


Good point; I've added support for old requests.

> "http://www.gnu.org translation team" should be plural (teams)


I think so, and "gnu.org portion"; also, "&" should be "&amp;".
I don't feel confident enough to modify the database with my
own hands.

Pavel Kharitonov <ineiev>
Site Administrator
Fri 31 May 2013 09:33:18 PM UTC, comment #4:

Hi Ineiev - wow, great. It's an excellent improvement. Here are the things that come to mind:

- it would be convenient if category name and project type were a link that brings up the jobs that are listed (the links that are on the current people/index.php).

- it would be convenient to have an "Any" category which just brings up all jobs in the selected project types -- or all project types if none/all are selected.

- the original request from Shailesh about simultaneously searching the three GNU categories was (I think) so we could use that link on various web pages (help GNU/GNU todo/GNU tasks/etc.). We shouldn't forget to actually make use of the new functionality when it is live :).

- "http://www.gnu.org translation team" should be plural (teams). Maybe the name can be updated in whatever db it's in?

wdyt?

Thanks,
Karl

Karl Berry <karl>
Site Administrator
Fri 31 May 2013 08:13:04 PM UTC, comment #3:

I've just written a draft, https://savannah.gnu.org/people/1index.php.

Pavel Kharitonov <ineiev>
Site Administrator
Sun 24 Apr 2011 04:38:36 PM UTC, comment #2:

Yes, this functionality would be need to be implemented via a code change. I'll add that to my to-do list.

Michael J. Flickinger <mjflick>
Site Administrator
Sun 17 Apr 2011 10:33:07 PM UTC, comment #1:

Shailesh, sorry for the delay ... this was still on my list to ask Michael about. As for your direct question here, I think the answer is no; at least, I've never heard of any such "aggregation" query.

Michael, what we want to do is have a single query/url which displays all the official GNU-related jobs -- the three types that Shailesh lists below. Any ideas about how to approach this? Maybe a new type_id which gets handled specially in the back end?

Thanks,
Karl

Karl Berry <karl>
Site Administrator
Sun 17 Apr 2011 11:03:52 AM UTC, original submission:

Is there any way to view the 'job list' of multiple project types on single page using single link.

For example:
https://savannah.gnu.org/people/?type_id=1,3,6
Single link showing 'job list' of all jobs in 'Official GNU software' + 'http://www.gnu.org portion' + 'http://www.gnu.org translation'

shailesh <shailesh_ghadge>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #28823:  frontend.diff added by ineiev (441B - application/octet-stream)
file #28824:  savane-refs.diff added by ineiev (4kB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by ineiev (Posted a comment)
  • -unavailable- added by mjflick (Posted a comment)
  • -unavailable- added by karl (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 20 Aug 2013 10:33:21 AM UTCineievCategoryNone=>Savannah website
      StatusNone=>Done
      Open/ClosedOpen=>Closed
    Mon 12 Aug 2013 04:52:34 PM UTCineievAttached File-=>Added frontend.diff, #28823
      Attached File-=>Added savane-refs.diff, #28824
    Mon 12 Aug 2013 04:45:54 PM UTCineievCarbon-CopyRemoved 81343=>-

    Back to the top


    Powered by Savane 3.1-cleanup