Next steps after initial commit

[Fabian Christ <ch...@googlemail.com>]

Hi,

I would like to discuss the next steps which are required after
Bertrand did the initial code import from the IKS Google repo. (Thanks
Bertrand!)

IMO the next steps are:

1) Decision about stanbol module names (discussion started)
2) Decision about new SVN structure (discussion started)
3) Restructure the SVN
4) Redefine the package structure starting with "org.apache.stanbol"
5) Add license headers to source files
6) Define a structure + content for stanbol website
7) Define a stanbol website layout
8) Update/extend the initial stanbol website

What do you think? I am not sure if people define deadlines for those
steps in an open source project but IMO it would be nice to define
some timeline.

Best
-- 
Fabian

Re: Next steps after initial commit

[Umesh Awasthi <um...@gmail.com>]

I am agree what Fabian about defining the road map so any new one can just
step in and can move ahead

On Wed, Dec 1, 2010 at 7:15 PM, Fabian Christ
<ch...@googlemail.com>wrote:

> Hi,
>
> yes, defining goals seems to be really better and more motivating than
> speaking in (necessary) steps.
>
> 2010/12/1 Bertrand Delacretaz <bd...@apache.org>:
> > 1. Provide a simple way for developers to test our modules (can
> > require building from svn initially)
> > 2. Describe those modules on the website, at the "how to test this in
> > 15 minutes" level
> > 3. Make a first incubator release (requires some code cleanup to match
> > ASF requirements)
>
> I think these goals are fine. I would suggest one more goal - not sure
> about the ordering:
>
> X. Explain other developers/visitors/contributers our roadmap and
> plans for the future to give people an idea where we need help.
>
> --
> Fabian
>



-- 
With Regards
Umesh Awasthi
Software Engineers never die… They just go Offline
http://travelling-rants.blogspot.com/

Re: Next steps after initial commit

[Fabian Christ <ch...@googlemail.com>]

Hi,

yes, defining goals seems to be really better and more motivating than
speaking in (necessary) steps.

2010/12/1 Bertrand Delacretaz <bd...@apache.org>:
> 1. Provide a simple way for developers to test our modules (can
> require building from svn initially)
> 2. Describe those modules on the website, at the "how to test this in
> 15 minutes" level
> 3. Make a first incubator release (requires some code cleanup to match
> ASF requirements)

I think these goals are fine. I would suggest one more goal - not sure
about the ordering:

X. Explain other developers/visitors/contributers our roadmap and
plans for the future to give people an idea where we need help.

-- 
Fabian

Re: Next steps after initial commit

[Olivier Grisel <ol...@ensta.org>]

2010/12/1 Bertrand Delacretaz <bd...@apache.org>:
> Hi Fabian,
>
> On Wed, Dec 1, 2010 at 1:22 PM, Fabian Christ
> <ch...@googlemail.com> wrote:
>> ...IMO the next steps are:
>>
>> 1) Decision about stanbol module names (discussion started)
>> 2) Decision about new SVN structure (discussion started)
>> 3) Restructure the SVN
>> 4) Redefine the package structure starting with "org.apache.stanbol"
>> 5) Add license headers to source files
>> 6) Define a structure + content for stanbol website
>> 7) Define a stanbol website layout
>> 8) Update/extend the initial stanbol website
>>
>> What do you think? I am not sure if people define deadlines for those
>> steps in an open source project but IMO it would be nice to define...
>
> Thanks for this, I agree with the steps overall but I wonder if we
> shouldn't start by defining goals rather than steps?
>
> IMO the initial high-level goals would be, in priority order:
>
> 1. Provide a simple way for developers to test our modules (can
> require building from svn initially)
> 2. Describe those modules on the website, at the "how to test this in
> 15 minutes" level
> 3. Make a first incubator release (requires some code cleanup to match
> ASF requirements)
>
> If we agree on that, we can derive a list of tasks that will probably
> match yours, but focusing on goals.
>
> I'd manage that in JIRA, first create issues that match the agreed
> upon goals and then create issues for the steps that lead us there.

+1

-- 
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel

Re: Next steps after initial commit

[Bertrand Delacretaz <bd...@apache.org>]

Hi Fabian,

On Wed, Dec 1, 2010 at 1:22 PM, Fabian Christ
<ch...@googlemail.com> wrote:
> ...IMO the next steps are:
>
> 1) Decision about stanbol module names (discussion started)
> 2) Decision about new SVN structure (discussion started)
> 3) Restructure the SVN
> 4) Redefine the package structure starting with "org.apache.stanbol"
> 5) Add license headers to source files
> 6) Define a structure + content for stanbol website
> 7) Define a stanbol website layout
> 8) Update/extend the initial stanbol website
>
> What do you think? I am not sure if people define deadlines for those
> steps in an open source project but IMO it would be nice to define...

Thanks for this, I agree with the steps overall but I wonder if we
shouldn't start by defining goals rather than steps?

IMO the initial high-level goals would be, in priority order:

1. Provide a simple way for developers to test our modules (can
require building from svn initially)
2. Describe those modules on the website, at the "how to test this in
15 minutes" level
3. Make a first incubator release (requires some code cleanup to match
ASF requirements)

If we agree on that, we can derive a list of tasks that will probably
match yours, but focusing on goals.

I'd manage that in JIRA, first create issues that match the agreed
upon goals and then create issues for the steps that lead us there.

Reaching goal 3. above with any svn structure and any website
organization is fine IMO, whereas it's easy to get stuck on
discussions regarding svn and website structure for example.

In other words, I'm fine producing results from a semi-chaotic
structure and refining later ;-)

-Bertrand