Though it might appear that my contributions in this thread visavis the
OFBiz aspect may look like adversity towards deployment on comdev svn so
the comdev community can work on it, I am +1

Regards

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Wed, Jan 14, 2015 at 6:53 PM, Ross Gardler (MS OPEN TECH) <
ross.gard...@microsoft.com> wrote:

> Daniel,
>
> There is no "assuming" just do it :-)
>
> You have a number of ComDev PMC members saying +1, and you are a PMC
> member yourself. Let's have the code where we can start working on it and
> let's get it to feature parity with projects.apache.org ASAP. I agree
> with Rich that there is value in this already.
>
> This is not to exclude the much broader OfBiz proposal, but it looks to me
> like this solution is close to being ready to go as a replacement for
> projects.apache.org and I already see some simple improvements I can make
> in a coffee break at work :-)
>
> Ross
>
> -----Original Message-----
> From: Daniel Gruno [mailto:humbed...@apache.org]
> Sent: Wednesday, January 14, 2015 9:43 AM
> To: dev@community.apache.org
> Subject: Re: projects.apache.org overhaul proposal
>
>
> On 2015-01-14 18:37, Jacques Le Roux wrote:
> > Just as a note for the sake of truth, OFBiz has Content component
> > http://projects.apache.pw/projects.html?category#content
>
> http://ofbiz.apache.org/doap_OFBiz.rdf disagrees ;-) but, assuming this
> gets accepted into comdev, you needn't worry about doap files any longer,
> as you will be able to edit it online instead.
>
> With regards,
> Daniel.
>
> >
> > I very like what I saw, kudos!
> >
> > Jacques
> >
> > Le 14/01/2015 12:48, Daniel Gruno a écrit :
> >> 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.
> >>
> >> 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.
> >>
> >> 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.
> >>
> >> With regards,
> >> Daniel.
> >>
> >>
> >>
>
>

Reply via email to