On 2015-01-14 14:40, Rich Bowen wrote:
On 01/14/2015 06:48 AM, Daniel Gruno wrote:
Hi folks,
I was having a conversation with Rich (Bowen) some weeks ago, and the
sentiment was that our projects page ( projects.apache.org
<http://projects.apache.org> ) could use a big overhaul. It's outdated,
not very user friendly, doesn't really compile the data into anything
useful (mostly just displays "raw" data) and it's difficult to navigate
(no search abilities, no actual overviews).
Therefore, I propose that the community development project takes over
this project from Infra, which has no interest in continuing/maintaining
it, and revamps it with both a new site design and a new LDAP/JSON-based
information system which would enable people to edit their project
details online without having to upload/change RDF files when something
happens. This would also mean that everything could be rendered in the
browser instead of relying on daily cron jobs to compile the page, and
also allow us to add some inspiring/interesting graphical charts and
overviews/timelines.
I have been working on a proposal that follows these ideas, which is
available for preview at http://projects.apache.pw/ for those
interested. Only the first two tabs in the menu currently work (and the
extensive search feature), but that is still most of what the old site
has and then some. I am pondering on moving some of the front page stuff
to the 'Timelines' tab instead, feedback is appreciated on this.
This is really cool stuff, and answers many of the questions that I go
hunting for every time I do a presentation about the ASF. I'm *sure*
I'll have feature requests going forward.
So, comments, feedback, questions, anything is most welcome, especially
comments on whether you:
1) think comdev should be responsible for the projects directory
2) think the proposal looks good/swell/nifty/whatever.
So, one thing you don't appear to mention ... what language is this
all written in. My biggest concern with this is that it, like the
first generation projects.a.o, might end up being another
single-developer, single-maintainer site, and thus end up being
unmaintained in short order. We want to avoid that.
The site itself is 100% static HTML+JavaScript, I haven't added any
arcane Lua/PHP/whatever scripts to it ;).
For the import and maintenance of data such a committer names, reporting
cycles and current chairs, there are 7 small python scripts that convert
existing data to JSON, some of which will need to run as cron jobs.
I hope this answers your question :)
With regards,
Daniel.
A few notes on the search feature:
- You can search for virtually anything within a project, types,
languages, descriptions, bug-trackers etc
- Try typing your committer ID or Apache ID into the box, and it will
show all projects you are a part of
If there is consensus for moving this into comdev framework and
collaborating on this, I will commit the proposal to a sub-folder in the
comdev svn repository and ask infra for a VM where we can set this up.
+1 to moving this into comdev svn, but I do want to hear an answer to
the above question. (Yes, I know, you've discussed this with me in
IRC, but I'd like to have details on the record so that other people
can step up and say, hey, I can do that!)
