Hi guys,
I know it's frustrating to wait for something that could be done in a
matter of minutes, but in the mean time, I would suggest you start some
discussions about some important aspects of the project, before it
starts to grow by adding ne committers :
1) discuss about the file formatting options :
- space vs tabs : usually, almost everyone ins using spaces, no tabs in
all the files.(4 spaces). This is not your case. It would be interesting
to states what's is to be used explicitly.
- Classes headers : @author can be added, it's up to you to decide what
to put into it
- formater : would you keep the default Java formatting, or do you have
some desires to modify it ?
As a rule of thumb, most of the ASF projects are using spaces/no tabs,
default Java format and @author only contains a ref to The ASF. This is
*not* mandatory...
2) DEFT Web site
- it would be a good idea to start thinking about a dedicated web-site
- should it be Confluence backed, or whatever the ASF is now using
(don't remember exactly what it is, Niklas ?)
- structure for this web-site (doco, downloads, tutorials, how to become
a committer, etc)
3) IP cleareance
I think it should be quite fast. The first step would be to clearly list
the initial committers, and to identify those who contributed to each
part of the code, getting an ICLA for them
- listing the dependencies, and their license
- if some code has been copied from third party projects, I would
seriously suggest that they should be replaced, unless it's Apache code
(you never know how tainted it was before you copied it...)
- Pick a Logo and add the TM to it (this is mandated by The ASF : the
Logo will be own by The ASF)
Looking at the code size, all those tasks should not take a long time,
and it's better to do it while the project is in its infancy at the ASF.
One last thing : I'm a Javadoc crazy freak. Most of the projects I see
around are just dry code without Javadoc, and Javadoc is the easiest way
to help new comers to get a grip about the code. I know it's a major
burden, like tests are, but, well, it just help. This is not really a
part of being a mentor, I just like beautiful code with good tests and
great Javadoc... Excuse me for that :)
Have fun this week-end !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com