You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Rahul Akolkar <ra...@gmail.com> on 2005/12/04 06:08:36 UTC
[all] Website changes (was Re: short critique of site)
I've posted a version of the Commons website in my ~ which contains a
"Dormant" section to match the Commons repository (some of the links
are absolute, so if you're clicking through, do make sure you're not
going out to jakarta.apache.org, if that matters):
http://people.apache.org/~rahul/commons/
Does anyone have further changes that they'd want to suggest before I
attach the patch? Are we removing the Korean/Japanese translation
links since they're broken/stale? The wiki link will go under "General
Information" (missed that).
I made up a little blurb about reviving dormant components at the
bottom of the following page, based on my memory about what the
process was. Anyone wants to contribute a formal blurb?
http://people.apache.org/~rahul/commons/dormant/index.html
Finally, does anyone using TortoiseSVN know how to create a patch that
contains new files? ;-)
-Rahul
On 12/3/05, Henri Yandell <fl...@gmail.com> wrote:
> On 12/3/05, Rahul Akolkar <ra...@gmail.com> wrote:
> >
<snip/>
> >
> > The current sandbox page [2] (and therefore Commons home page as well)
> > list them together, would there be any interest in separating the
> > "dormant" components so the website actually matches the repository? I
> > can post a patch for the website if there is interest.
>
> interest :)
>
> Hen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Rahul Akolkar <ra...@gmail.com>.
Please see three responses consolidated in one email below -
On 12/4/05, Stephen Colebourne <sc...@btopenworld.com> wrote:
> Rahul Akolkar wrote:
> > I've posted a version of the Commons website in my ~
<snip/>
> >
> > http://people.apache.org/~rahul/commons/
<snap/>
>
> "The Jakarta Commons project is composed of two parts:"
>
> that should be three now...
>
<snip/>
Ugh, thanks.
On 12/4/05, Henri Yandell <fl...@gmail.com> wrote:
> On 12/4/05, Rahul Akolkar <ra...@gmail.com> wrote:
>
<snap/>
> > Are we removing the Korean/Japanese translation
> > links since they're broken/stale? The wiki link will go under "General
> > Information" (missed that).
>
> +1 :)
>
<snip/>
OK, will remove those two links.
> I'll find out from Infra whether we can drop the direct links to the
> svn or not. It's messy having 6 links there.
>
<snap/>
Yup, its a bit of a clutter, let us know what infra says.
On 12/4/05, Martin Cooper <ma...@apache.org> wrote:
> On 12/4/05, Mario Ivankovits <ma...@ops.co.at> wrote:
> >
> > Martin van den Bemt wrote:
> > > Also have a look at http://people.apache.org/~mvdb/contributors.html
> > > which was automatically generated by maven, based on the all the
> > > developers sections in commons-proper.
> >
> > Should this be a list of contributers and/or committers?
<snip/>
>
> I have two concerns here. First, not all components maintain a contributor
> list in addition to the committer list, so any contributor list would be
> inherently inaccurate. Secondly, how do you define a contributor? Someone
> who posted a suggestion to the mailing list? Someone who points out a typo?
> Someone who provided a 1-line patch? A 100-line patch? Without a concrete
> definition, it's hard to know when we need to update project.xml when making
> a change.
>
> Therefore, I'd prefer to just list committers, if we need a list at all.
>
<snap/>
Agreed, for the same reasons that some at the ASF prefer source files
without @author tags.
-Rahul
>
> --
> Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Martin Cooper <ma...@apache.org>.
On 12/4/05, Mario Ivankovits <ma...@ops.co.at> wrote:
>
> Martin van den Bemt wrote:
> > Also have a look at http://people.apache.org/~mvdb/contributors.html
> > which was automatically generated by maven, based on the all the
> > developers sections in commons-proper.
> Should this be a list of contributers and/or committers?
> I ask as the headline talks about contributors but on the list are only
> committers. At least the VFS contributors are missing.
>
> If we are able to autogenerate this list, maybe we might list the
> contributors too.
I have two concerns here. First, not all components maintain a contributor
list in addition to the committer list, so any contributor list would be
inherently inaccurate. Secondly, how do you define a contributor? Someone
who posted a suggestion to the mailing list? Someone who points out a typo?
Someone who provided a 1-line patch? A 100-line patch? Without a concrete
definition, it's hard to know when we need to update project.xml when making
a change.
Therefore, I'd prefer to just list committers, if we need a list at all.
--
Martin Cooper
How did you create the "Emeritus" section?
> Is this list based on the (non) commits in the last year?
>
> I ask as e.g. adammurdoch is still on the list but I cant find a commit.
> I have no problem with him, but if we would like to have a correct
> status than this is a failure, isnt it? BTW I just checked the
> commons-dev commit messages, so maybe I missed something.
>
> ---
> Mario
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: [all] Website changes (was Re: short critique of site)
Posted by Martin Cooper <ma...@apache.org>.
On 12/5/05, Martin van den Bemt <ml...@mvdb.net> wrote:
>
> Hi Mario,
>
> Sorry for not being there on sunday to finish of the commit :)
> - The current list of contributors are only committers.
> - The committers are collected from the project.xml (the developers
> section in maven), so a lot more inactive people out there are probably
> listed.
> - Just the list of committers is generated. The current contributor page
> is split up in 2 parts : top and bottom. The emuritus committers are at the
> bottom.
> - I let maven glue the top, list of committers and bottom together.
> - You end up with a generated contributors.xml in the xdocs directory.
> - The generation is currently hooked into the commons-site-generate goal.
> - The generation itself happens in the commons-contributors-page-generate
> goal.
>
> A choices need to be made before commit :
>
> Do we want to generate the committers from the commons-site-generate goal
> ?
Sure. I see no reason not to do this.
or
> Do we want to generate this on demand by calling a specific goal (I'll
> rename the goal to something more friendly).
That just ensures that it will be out of date a lot of the time. ;-)
--
Martin Cooper
or
> Make both possible ?
>
> (I am currently reusing the list of loaded poms that the reactor stores in
> a variable)
>
> Mvgr,
> Martin
>
>
> Mario Ivankovits wrote:
> > Martin van den Bemt wrote:
> >
> >> Also have a look at http://people.apache.org/~mvdb/contributors.html
> >> which was automatically generated by maven, based on the all the
> >> developers sections in commons-proper.
> >
> > Should this be a list of contributers and/or committers?
> > I ask as the headline talks about contributors but on the list are only
> > committers. At least the VFS contributors are missing.
> >
> > If we are able to autogenerate this list, maybe we might list the
> > contributors too.
> >
> > How did you create the "Emeritus" section?
> > Is this list based on the (non) commits in the last year?
> >
> > I ask as e.g. adammurdoch is still on the list but I cant find a commit.
> > I have no problem with him, but if we would like to have a correct
> > status than this is a failure, isnt it? BTW I just checked the
> > commons-dev commit messages, so maybe I missed something.
> >
> > ---
> > Mario
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: [all] Website changes (was Re: short critique of site)
Posted by Martin van den Bemt <ml...@mvdb.net>.
Yep it requires a checkout of trunks-proper, not doing any fancy stuff with scm, but if you build the commons site it is required anyway to have a checkout of that, so no new problems are introduced at least..
I'll enable the generation of the contributors.xml file and will commit the new one :)
Mvgr,
Martin
Phil Steitz wrote:
> On 12/5/05, Martin van den Bemt <ml...@mvdb.net> wrote:
>
>>Hi Mario,
>>
>>Sorry for not being there on sunday to finish of the commit :)
>>- The current list of contributors are only committers.
>>- The committers are collected from the project.xml (the developers section in maven), so a lot more inactive people out there are probably listed.
>>- Just the list of committers is generated. The current contributor page is split up in 2 parts : top and bottom. The emuritus committers are at the bottom.
>>- I let maven glue the top, list of committers and bottom together.
>>- You end up with a generated contributors.xml in the xdocs directory.
>>- The generation is currently hooked into the commons-site-generate goal.
>>- The generation itself happens in the commons-contributors-page-generate goal.
>>
>>A choices need to be made before commit :
>>
>>Do we want to generate the committers from the commons-site-generate goal ?
>> or
>>Do we want to generate this on demand by calling a specific goal (I'll rename the goal to something more friendly).
>> or
>>Make both possible ?
>
>
> I agree with Martin C that it will be more likely kept up to date if
> it is automatic.
>
>>(I am currently reusing the list of loaded poms that the reactor stores in a variable)
>>
>
> Will this require that to gen the commons site you will need to have
> trunks-proper checked out with the standard directory layout? I am OK
> with this personally, just wondering if it could ever cause problems.
> Also, one would need to have all svn upped to be correct. Or are you
> doing something clever with the scm plugin to just grab the POMS at
> gen time?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Phil Steitz <ph...@gmail.com>.
On 12/5/05, Martin van den Bemt <ml...@mvdb.net> wrote:
> Hi Mario,
>
> Sorry for not being there on sunday to finish of the commit :)
> - The current list of contributors are only committers.
> - The committers are collected from the project.xml (the developers section in maven), so a lot more inactive people out there are probably listed.
> - Just the list of committers is generated. The current contributor page is split up in 2 parts : top and bottom. The emuritus committers are at the bottom.
> - I let maven glue the top, list of committers and bottom together.
> - You end up with a generated contributors.xml in the xdocs directory.
> - The generation is currently hooked into the commons-site-generate goal.
> - The generation itself happens in the commons-contributors-page-generate goal.
>
> A choices need to be made before commit :
>
> Do we want to generate the committers from the commons-site-generate goal ?
> or
> Do we want to generate this on demand by calling a specific goal (I'll rename the goal to something more friendly).
> or
> Make both possible ?
I agree with Martin C that it will be more likely kept up to date if
it is automatic.
>
> (I am currently reusing the list of loaded poms that the reactor stores in a variable)
>
Will this require that to gen the commons site you will need to have
trunks-proper checked out with the standard directory layout? I am OK
with this personally, just wondering if it could ever cause problems.
Also, one would need to have all svn upped to be correct. Or are you
doing something clever with the scm plugin to just grab the POMS at
gen time?
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Martin van den Bemt <ml...@mvdb.net>.
Hi Mario,
Sorry for not being there on sunday to finish of the commit :)
- The current list of contributors are only committers.
- The committers are collected from the project.xml (the developers section in maven), so a lot more inactive people out there are probably listed.
- Just the list of committers is generated. The current contributor page is split up in 2 parts : top and bottom. The emuritus committers are at the bottom.
- I let maven glue the top, list of committers and bottom together.
- You end up with a generated contributors.xml in the xdocs directory.
- The generation is currently hooked into the commons-site-generate goal.
- The generation itself happens in the commons-contributors-page-generate goal.
A choices need to be made before commit :
Do we want to generate the committers from the commons-site-generate goal ?
or
Do we want to generate this on demand by calling a specific goal (I'll rename the goal to something more friendly).
or
Make both possible ?
(I am currently reusing the list of loaded poms that the reactor stores in a variable)
Mvgr,
Martin
Mario Ivankovits wrote:
> Martin van den Bemt wrote:
>
>> Also have a look at http://people.apache.org/~mvdb/contributors.html
>> which was automatically generated by maven, based on the all the
>> developers sections in commons-proper.
>
> Should this be a list of contributers and/or committers?
> I ask as the headline talks about contributors but on the list are only
> committers. At least the VFS contributors are missing.
>
> If we are able to autogenerate this list, maybe we might list the
> contributors too.
>
> How did you create the "Emeritus" section?
> Is this list based on the (non) commits in the last year?
>
> I ask as e.g. adammurdoch is still on the list but I cant find a commit.
> I have no problem with him, but if we would like to have a correct
> status than this is a failure, isnt it? BTW I just checked the
> commons-dev commit messages, so maybe I missed something.
>
> ---
> Mario
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Mario Ivankovits <ma...@ops.co.at>.
Martin van den Bemt wrote:
> Also have a look at http://people.apache.org/~mvdb/contributors.html
> which was automatically generated by maven, based on the all the
> developers sections in commons-proper.
Should this be a list of contributers and/or committers?
I ask as the headline talks about contributors but on the list are only
committers. At least the VFS contributors are missing.
If we are able to autogenerate this list, maybe we might list the
contributors too.
How did you create the "Emeritus" section?
Is this list based on the (non) commits in the last year?
I ask as e.g. adammurdoch is still on the list but I cant find a commit.
I have no problem with him, but if we would like to have a correct
status than this is a failure, isnt it? BTW I just checked the
commons-dev commit messages, so maybe I missed something.
---
Mario
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Martin van den Bemt <ml...@mvdb.net>.
Also have a look at http://people.apache.org/~mvdb/contributors.html which was automatically generated by maven, based on the all the developers sections in commons-proper.
Mvgr,
Martin
Rahul Akolkar wrote:
> I've posted a version of the Commons website in my ~ which contains a
> "Dormant" section to match the Commons repository (some of the links
> are absolute, so if you're clicking through, do make sure you're not
> going out to jakarta.apache.org, if that matters):
>
> http://people.apache.org/~rahul/commons/
>
> Does anyone have further changes that they'd want to suggest before I
> attach the patch? Are we removing the Korean/Japanese translation
> links since they're broken/stale? The wiki link will go under "General
> Information" (missed that).
>
> I made up a little blurb about reviving dormant components at the
> bottom of the following page, based on my memory about what the
> process was. Anyone wants to contribute a formal blurb?
>
> http://people.apache.org/~rahul/commons/dormant/index.html
>
> Finally, does anyone using TortoiseSVN know how to create a patch that
> contains new files? ;-)
>
> -Rahul
>
>
> On 12/3/05, Henri Yandell <fl...@gmail.com> wrote:
>
>>On 12/3/05, Rahul Akolkar <ra...@gmail.com> wrote:
>>
> <snip/>
>
>>>The current sandbox page [2] (and therefore Commons home page as well)
>>>list them together, would there be any interest in separating the
>>>"dormant" components so the website actually matches the repository? I
>>>can post a patch for the website if there is interest.
>>
>>interest :)
>>
>>Hen
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Rahul Akolkar <ra...@gmail.com>.
On 12/10/05, Henri Yandell <fl...@gmail.com> wrote:
<snip/>
>
> Just talked with Leo. We can drop the direct links and just use viewcvs.
>
> The big problems are:
>
> a) cvsgrab tool, which is effectively a viewcvs scraper
> b) using viewcvs for the site. ie) not publishing the site and just
> hooking the nav into the latest release in viewcvs :)
>
> So feel free to go ahead and reduce the links.
>
<snap/>
Done.
-Rahul
> Hen
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Henri Yandell <fl...@gmail.com>.
On 12/4/05, Henri Yandell <fl...@gmail.com> wrote:
> On 12/4/05, Rahul Akolkar <ra...@gmail.com> wrote:
>
> > Does anyone have further changes that they'd want to suggest before I
> > attach the patch? Are we removing the Korean/Japanese translation
> > links since they're broken/stale? The wiki link will go under "General
> > Information" (missed that).
>
> +1 :)
>
> I'll find out from Infra whether we can drop the direct links to the
> svn or not. It's messy having 6 links there.
Just talked with Leo. We can drop the direct links and just use viewcvs.
The big problems are:
a) cvsgrab tool, which is effectively a viewcvs scraper
b) using viewcvs for the site. ie) not publishing the site and just
hooking the nav into the latest release in viewcvs :)
So feel free to go ahead and reduce the links.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Henri Yandell <fl...@gmail.com>.
On 12/4/05, Rahul Akolkar <ra...@gmail.com> wrote:
> Does anyone have further changes that they'd want to suggest before I
> attach the patch? Are we removing the Korean/Japanese translation
> links since they're broken/stale? The wiki link will go under "General
> Information" (missed that).
+1 :)
I'll find out from Infra whether we can drop the direct links to the
svn or not. It's messy having 6 links there.
> I made up a little blurb about reviving dormant components at the
> bottom of the following page, based on my memory about what the
> process was. Anyone wants to contribute a formal blurb?
>
> http://people.apache.org/~rahul/commons/dormant/index.html
>
> Finally, does anyone using TortoiseSVN know how to create a patch that
> contains new files? ;-)
Sounds like we'll give you commit access instead. Sorry.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] Website changes (was Re: short critique of site)
Posted by Stephen Colebourne <sc...@btopenworld.com>.
Rahul Akolkar wrote:
> I've posted a version of the Commons website in my ~ which contains a
> "Dormant" section to match the Commons repository (some of the links
> are absolute, so if you're clicking through, do make sure you're not
> going out to jakarta.apache.org, if that matters):
>
> http://people.apache.org/~rahul/commons/
>
> Does anyone have further changes that they'd want to suggest before I
> attach the patch?
"The Jakarta Commons project is composed of two parts:"
that should be three now...
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org