incubator-alois-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <>
Subject Re: Podling report
Date Tue, 05 Oct 2010 09:06:31 GMT
> First of all, thanks for your engagement!

No problem :-)

> I added our first Report to,
> please tell me if more information is needed.

You should add that we have enabled the mailinglists and JIRA already.

> * How can I modify
> (Emailadresses of mailinglists are misspelled)

This is bein done by your mentors.
I found the error and will fix it tomorrow morning (or Scott, if he is
quicker :-))

> * I could not find a page that describes real requirements for the sourcecode
> to work in apache environement. (E.g. what licensing header is needed, how
> should test cases run and what is required for automatic builds?)

Except with licensing header its up to the project what infra they choose.


Basically the license needs to be in every sourcefile.

About unittesting and cruise control - decide yourself what your
project standard is. Apache is offering several build machines like
buildbot, i think cruisecontrol and gump. You can discuss pros and
cons on your project mailinglists or ask infrastructure@a.o when its
going to be more concrete.

> * How do I get a user account for uploading sourcecode?

Once you CLA has arrived and is listet here:
your mentors will request an Apache account for you (and your team)
After that you have access to your svn repository and webspace.

> Possibly I searched the wrong places, probably a quick link list for beginners
> could help. ;-)

No problem - mentors are here to guide you.
Here is more info:

Let me know if any more questions.

> Thanks in advance.
> Best
> Flavio
> On Tuesday 05 October 2010 08:42:20 Christian Grobmeier wrote:
>> Hello,
>> ...and warm greetings to the brandnew ALOIS dev list.
>> I hope everybody from the core team has made it to subscribe to this
>> list - a short feedback is welcome.
>> I would like to mention that ALOIS has to provide a incubator report
>> each months for the first three and then quarterly. The next one is to
>> be done now.
>> Here is the reporting schedule:
>> A report should be added to the wiki:
>> You should include this information:
>> - The "incubating since" info.
>> - The project's top 2 or 3 things to resolve prior to graduation.
>> - A short description of what your project's software does.
>> In other terms projects report what they are doing currently, how life
>> goes on and if there are any big discussions/problems.
>> It would be very good if one of you guys would create even the first
>> report. Mentors will review or help in case of trouble. Please have
>> also in mind that the mentors need to sign off the report, so please
>> give us some time before deadline to check it out. 50% of your mentors
>> have childs, the other 50% horses and that means we are not on our
>> computer all the day :-)
>> Just a side note, reports should be in time; incubator people watch
>> them seriously and a failed report is maybe the first sign for a
>> project in trouble. If you want to show your apache friends that ALOIS
>> is doing well - make a good report :-)
>> If any questions, shout.
>> Cheers to all,
>> Christian

View raw message