You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Benson Margulies <bi...@gmail.com> on 2011/09/16 20:28:39 UTC
Moving the incubator web site to the CMS
In an effort to reduce the number of procedures vying for neurons in
my memory, I think it would be good if we went ahead and CMS-ed the
incubator website. I'm willing to help Joe with this, and he suggested
that I post this message looking for other contributors to the effort.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by Benson Margulies <bi...@gmail.com>.
On Sat, Sep 17, 2011 at 1:03 PM, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Hi...
>
> On Fri, Sep 16, 2011 at 9:03 PM, sebb <se...@gmail.com> wrote:
>> On 16 September 2011 19:28, Benson Margulies <bi...@gmail.com> wrote:
>>> In an effort to reduce the number of procedures vying for neurons in
>>> my memory, I think it would be good if we went ahead and CMS-ed the
>>> incubator website. I'm willing to help Joe with this, and he suggested
>>> that I post this message looking for other contributors to the effort.
>
> Please count me in. Did you discuss any procedures for this effort, I
> mean are we going to do it manually or we need to automate it somehow
> ?
My foggy recollection was that this was discussed quite some time ago.
The idea here is *not* to touch or impose on the podlings themselves,
who have always been free to roll their sites as they will within the
overall policy.
>
>>
>> The incubator site currently in incubator/public/trunk is the source
>> for only part of the files under /www/incubator.apache.org/.
>> The other files are either maintained manually by podlings, or some
>> use svn pub sub.
>>
>> Is that mixture going to cause a problem?
>> Perhaps it would be worth considering rearranging the layout so that
>> the podling trees were distinct from the main incubator site and
>> status files.
>
> I think that would be easier when it is CMSed, AFAIU of how the CMS
> works, for new podlings write access would be given to Mentors and
> they will have to add/update relevant Incubator pages which is more
> easy to do on CMS.
>
>>
>> Also, what about clutch? That currently depends on being able to read
>> some XML files.
>
> Although I have another long term idea for that, but it can be updated
> to read the relevant pages of Incubator CMS, and I am also very
> willing to help in that.
>
>>
>> There is a lot of work involved in converting everything successfully.
>
> Indeed, thats why Benson is asking for contributors ;).
>
>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi Sebb...
Apologies for being away from this thread, is there any place where
I can help in this task ?
I noticed other threads related to this one, I am also having a look at it.
On Tue, Sep 20, 2011 at 12:24 PM, sebb <se...@gmail.com> wrote:
> On 20 September 2011 04:24, David Crossley <cr...@apache.org> wrote:
>> sebb wrote:
>>> Mohammad Nour El-Din
>>> >sebb wrote:
>>> >>
>>> >> Also, what about clutch? That currently depends on being able to read
>>> >> some XML files.
>>> >
>>> > Although I have another long term idea for that, but it can be updated
>>> > to read the relevant pages of Incubator CMS, and I am also very
>>> > willing to help in that.
>>
>> Parts of Clutch have been modified at various occasions
>> to gather its data and hints from other places.
>>
>> It currently gets facts from
>> http://wiki.apache.org/incubator/ReportingSchedule
>> and from the xml source for
>> http://incubator.apache.org/projects/
>>
>> Then it tries to get some hints from the xml source of
>> each podling status page. Then it uses those gathered hints
>> to detect whether the various project resources are available.
>>
>> After the move to CMS, it could parse the generated html instead.
>> As Sebb indicates, the Markdown source files would not be easy.
>>
>>> I think we should base clutch on a separate simple summary file, which
>>> is then used to create various aspects of the CMS site, as well as
>>> being used for other purpose. The CMS syntax is very flexible, and
>>> harder to parse.
>>>
>>> Having a purpose-designed podling status file would make Clutch's job
>>> much easier, as well as being easier to edit.
>>> For example, now when a podling graduates, the entry has to be moved
>>> from one section to another.
>>> A dedicated status file would just required changing the status entry.
>>
>> Yes. However, could we please make it so that
>> that summary file is separate to Clutch.
>
> Agreed.
>
>> The summary file needs other reasons for being,
>> which might also encourage it to be well-maintained.
>
> My intention was originally for it to be the source of the projects
> page, i.e. it would be directly updated by podlings, and used to
> generate the projects index page and the RHS links. One file to update
> instead of two, though podlings would still need to update their own
> pages as at present.
>
> It would need to contain the following as a minimum:
> Project Description Apache Sponsor Mentors Started [Ended] Status
>
> If it's decided to use DOAPs for individual podling status pages, then
> the description and perhaps other fields could be automatically taken
> from the DOAP and merged into the summary file. It might even be
> possible to create the entire file from the DOAPs, but it might still
> be useful to list the podling names as a cross-check, and for historic
> projects it would be easier not to have to create DOAPS.
>
> It would then only be necessary to update the summary file when the
> podling status changed: creation, graduation, retirement or
> hibernation, assuming that is not done in the DOAP files themselves.
>
>> I am running low on volunteer time, but will attempt to
>> adjust Clutch to follow the CMS changes, taking small
>> steps where possible.
>
> Once the new file format is decided, futher changes to Clutch should be minimal.
>
>> -David
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by sebb <se...@gmail.com>.
On 20 September 2011 04:24, David Crossley <cr...@apache.org> wrote:
> sebb wrote:
>> Mohammad Nour El-Din
>> >sebb wrote:
>> >>
>> >> Also, what about clutch? That currently depends on being able to read
>> >> some XML files.
>> >
>> > Although I have another long term idea for that, but it can be updated
>> > to read the relevant pages of Incubator CMS, and I am also very
>> > willing to help in that.
>
> Parts of Clutch have been modified at various occasions
> to gather its data and hints from other places.
>
> It currently gets facts from
> http://wiki.apache.org/incubator/ReportingSchedule
> and from the xml source for
> http://incubator.apache.org/projects/
>
> Then it tries to get some hints from the xml source of
> each podling status page. Then it uses those gathered hints
> to detect whether the various project resources are available.
>
> After the move to CMS, it could parse the generated html instead.
> As Sebb indicates, the Markdown source files would not be easy.
>
>> I think we should base clutch on a separate simple summary file, which
>> is then used to create various aspects of the CMS site, as well as
>> being used for other purpose. The CMS syntax is very flexible, and
>> harder to parse.
>>
>> Having a purpose-designed podling status file would make Clutch's job
>> much easier, as well as being easier to edit.
>> For example, now when a podling graduates, the entry has to be moved
>> from one section to another.
>> A dedicated status file would just required changing the status entry.
>
> Yes. However, could we please make it so that
> that summary file is separate to Clutch.
Agreed.
> The summary file needs other reasons for being,
> which might also encourage it to be well-maintained.
My intention was originally for it to be the source of the projects
page, i.e. it would be directly updated by podlings, and used to
generate the projects index page and the RHS links. One file to update
instead of two, though podlings would still need to update their own
pages as at present.
It would need to contain the following as a minimum:
Project Description Apache Sponsor Mentors Started [Ended] Status
If it's decided to use DOAPs for individual podling status pages, then
the description and perhaps other fields could be automatically taken
from the DOAP and merged into the summary file. It might even be
possible to create the entire file from the DOAPs, but it might still
be useful to list the podling names as a cross-check, and for historic
projects it would be easier not to have to create DOAPS.
It would then only be necessary to update the summary file when the
podling status changed: creation, graduation, retirement or
hibernation, assuming that is not done in the DOAP files themselves.
> I am running low on volunteer time, but will attempt to
> adjust Clutch to follow the CMS changes, taking small
> steps where possible.
Once the new file format is decided, futher changes to Clutch should be minimal.
> -David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by David Crossley <cr...@apache.org>.
sebb wrote:
> Mohammad Nour El-Din
> >sebb wrote:
> >>
> >> Also, what about clutch? That currently depends on being able to read
> >> some XML files.
> >
> > Although I have another long term idea for that, but it can be updated
> > to read the relevant pages of Incubator CMS, and I am also very
> > willing to help in that.
Parts of Clutch have been modified at various occasions
to gather its data and hints from other places.
It currently gets facts from
http://wiki.apache.org/incubator/ReportingSchedule
and from the xml source for
http://incubator.apache.org/projects/
Then it tries to get some hints from the xml source of
each podling status page. Then it uses those gathered hints
to detect whether the various project resources are available.
After the move to CMS, it could parse the generated html instead.
As Sebb indicates, the Markdown source files would not be easy.
> I think we should base clutch on a separate simple summary file, which
> is then used to create various aspects of the CMS site, as well as
> being used for other purpose. The CMS syntax is very flexible, and
> harder to parse.
>
> Having a purpose-designed podling status file would make Clutch's job
> much easier, as well as being easier to edit.
> For example, now when a podling graduates, the entry has to be moved
> from one section to another.
> A dedicated status file would just required changing the status entry.
Yes. However, could we please make it so that
that summary file is separate to Clutch.
The summary file needs other reasons for being,
which might also encourage it to be well-maintained.
I am running low on volunteer time, but will attempt to
adjust Clutch to follow the CMS changes, taking small
steps where possible.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi...
On Sat, Sep 17, 2011 at 7:23 PM, sebb <se...@gmail.com> wrote:
> On 17 September 2011 18:03, Mohammad Nour El-Din
> <no...@gmail.com> wrote:
>> Hi...
>>
>> On Fri, Sep 16, 2011 at 9:03 PM, sebb <se...@gmail.com> wrote:
>>> On 16 September 2011 19:28, Benson Margulies <bi...@gmail.com> wrote:
>>>> In an effort to reduce the number of procedures vying for neurons in
>>>> my memory, I think it would be good if we went ahead and CMS-ed the
>>>> incubator website. I'm willing to help Joe with this, and he suggested
>>>> that I post this message looking for other contributors to the effort.
>>
>> Please count me in. Did you discuss any procedures for this effort, I
>> mean are we going to do it manually or we need to automate it somehow
>> ?
>>
>>>
>>> The incubator site currently in incubator/public/trunk is the source
>>> for only part of the files under /www/incubator.apache.org/.
>>> The other files are either maintained manually by podlings, or some
>>> use svn pub sub.
>>>
>>> Is that mixture going to cause a problem?
>>> Perhaps it would be worth considering rearranging the layout so that
>>> the podling trees were distinct from the main incubator site and
>>> status files.
>>
>> I think that would be easier when it is CMSed, AFAIU of how the CMS
>> works, for new podlings write access would be given to Mentors and
>> they will have to add/update relevant Incubator pages which is more
>> easy to do on CMS.
>
> I was referring to the fact that the podling *web-site* is at
>
> /incubator/podling
>
> which is part of the Incubator site.
>
> There should be no problem updating podling *status pages* under
> /incubator/projects/, which are part of the incubator/public SVN.
My wrong :).
>
> However, /incubator/podling *web sites* are created in various
> different ways and have different SVN source.
> Apart from the huge extra conversion effort, I don't think we should
> force podlings to use CMS.
>
>>>
>>> Also, what about clutch? That currently depends on being able to read
>>> some XML files.
>>
>> Although I have another long term idea for that, but it can be updated
>> to read the relevant pages of Incubator CMS, and I am also very
>> willing to help in that.
>
> I think we should base clutch on a separate simple summary file, which
> is then used to create various aspects of the CMS site, as well as
> being used for other purpose. The CMS syntax is very flexible, and
> harder to parse.
>
> Having a purpose-designed podling status file would make Clutch's job
> much easier, as well as being easier to edit.
> For example, now when a podling graduates, the entry has to be moved
> from one section to another.
> A dedicated status file would just required changing the status entry.
>
>>>
>>> There is a lot of work involved in converting everything successfully.
>>
>> Indeed, thats why Benson is asking for contributors ;).
>>
>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Thanks
>> - Mohammad Nour
>> ----
>> "Life is like riding a bicycle. To keep your balance you must keep moving"
>> - Albert Einstein
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by sebb <se...@gmail.com>.
On 17 September 2011 18:03, Mohammad Nour El-Din
<no...@gmail.com> wrote:
> Hi...
>
> On Fri, Sep 16, 2011 at 9:03 PM, sebb <se...@gmail.com> wrote:
>> On 16 September 2011 19:28, Benson Margulies <bi...@gmail.com> wrote:
>>> In an effort to reduce the number of procedures vying for neurons in
>>> my memory, I think it would be good if we went ahead and CMS-ed the
>>> incubator website. I'm willing to help Joe with this, and he suggested
>>> that I post this message looking for other contributors to the effort.
>
> Please count me in. Did you discuss any procedures for this effort, I
> mean are we going to do it manually or we need to automate it somehow
> ?
>
>>
>> The incubator site currently in incubator/public/trunk is the source
>> for only part of the files under /www/incubator.apache.org/.
>> The other files are either maintained manually by podlings, or some
>> use svn pub sub.
>>
>> Is that mixture going to cause a problem?
>> Perhaps it would be worth considering rearranging the layout so that
>> the podling trees were distinct from the main incubator site and
>> status files.
>
> I think that would be easier when it is CMSed, AFAIU of how the CMS
> works, for new podlings write access would be given to Mentors and
> they will have to add/update relevant Incubator pages which is more
> easy to do on CMS.
I was referring to the fact that the podling *web-site* is at
/incubator/podling
which is part of the Incubator site.
There should be no problem updating podling *status pages* under
/incubator/projects/, which are part of the incubator/public SVN.
However, /incubator/podling *web sites* are created in various
different ways and have different SVN source.
Apart from the huge extra conversion effort, I don't think we should
force podlings to use CMS.
>>
>> Also, what about clutch? That currently depends on being able to read
>> some XML files.
>
> Although I have another long term idea for that, but it can be updated
> to read the relevant pages of Incubator CMS, and I am also very
> willing to help in that.
I think we should base clutch on a separate simple summary file, which
is then used to create various aspects of the CMS site, as well as
being used for other purpose. The CMS syntax is very flexible, and
harder to parse.
Having a purpose-designed podling status file would make Clutch's job
much easier, as well as being easier to edit.
For example, now when a podling graduates, the entry has to be moved
from one section to another.
A dedicated status file would just required changing the status entry.
>>
>> There is a lot of work involved in converting everything successfully.
>
> Indeed, thats why Benson is asking for contributors ;).
>
>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> --
> Thanks
> - Mohammad Nour
> ----
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by Mohammad Nour El-Din <no...@gmail.com>.
Hi...
On Fri, Sep 16, 2011 at 9:03 PM, sebb <se...@gmail.com> wrote:
> On 16 September 2011 19:28, Benson Margulies <bi...@gmail.com> wrote:
>> In an effort to reduce the number of procedures vying for neurons in
>> my memory, I think it would be good if we went ahead and CMS-ed the
>> incubator website. I'm willing to help Joe with this, and he suggested
>> that I post this message looking for other contributors to the effort.
Please count me in. Did you discuss any procedures for this effort, I
mean are we going to do it manually or we need to automate it somehow
?
>
> The incubator site currently in incubator/public/trunk is the source
> for only part of the files under /www/incubator.apache.org/.
> The other files are either maintained manually by podlings, or some
> use svn pub sub.
>
> Is that mixture going to cause a problem?
> Perhaps it would be worth considering rearranging the layout so that
> the podling trees were distinct from the main incubator site and
> status files.
I think that would be easier when it is CMSed, AFAIU of how the CMS
works, for new podlings write access would be given to Mentors and
they will have to add/update relevant Incubator pages which is more
easy to do on CMS.
>
> Also, what about clutch? That currently depends on being able to read
> some XML files.
Although I have another long term idea for that, but it can be updated
to read the relevant pages of Incubator CMS, and I am also very
willing to help in that.
>
> There is a lot of work involved in converting everything successfully.
Indeed, thats why Benson is asking for contributors ;).
>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Thanks
- Mohammad Nour
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by sebb <se...@gmail.com>.
On 16 September 2011 19:28, Benson Margulies <bi...@gmail.com> wrote:
> In an effort to reduce the number of procedures vying for neurons in
> my memory, I think it would be good if we went ahead and CMS-ed the
> incubator website. I'm willing to help Joe with this, and he suggested
> that I post this message looking for other contributors to the effort.
The incubator site currently in incubator/public/trunk is the source
for only part of the files under /www/incubator.apache.org/.
The other files are either maintained manually by podlings, or some
use svn pub sub.
Is that mixture going to cause a problem?
Perhaps it would be worth considering rearranging the layout so that
the podling trees were distinct from the main incubator site and
status files.
Also, what about clutch? That currently depends on being able to read
some XML files.
There is a lot of work involved in converting everything successfully.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Moving the incubator web site to the CMS
Posted by David Crossley <cr...@apache.org>.
Benson Margulies wrote:
>
> In an effort to reduce the number of procedures vying for neurons in
> my memory, I think it would be good if we went ahead and CMS-ed the
> incubator website. I'm willing to help Joe with this, and he suggested
> that I post this message looking for other contributors to the effort.
I found some of the old threads:
Subject: CMS for the Incubator?
Date: 2010-10-12
To: private incubator.apache.org
Subject: [DISCUSS] starting the CMS migration process
Date: 2011-01-11
To: general incubator.apache.org
Subject: [CMS] handling tables and other complex html
Date: 2010-10-16
To: site-dev apache.org
The Incubator uses various tables. The latter thread
suggests some ways to handle those.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org