Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Developer Meeting on 2003-03-07

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Ladislav Hagara <hgr AT vabo.cz>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Developer Meeting on 2003-03-07
  • Date: Tue, 09 Mar 2004 11:15:31 +0100

> I have already opened the position :)

We might grand the position according to his/her work. It should be a
compliment
for his/her.
It is funny if we give out the possitions carelessly. Leader of ... is open,
who
want it ?

> it should be someone with a long term interest in SMGL

We need a fresh blood.
Who is more useful for SMGL? Active developer or someone with a long term
interest
in SMGL?
Of course we all prefer the active developers with a long term interest in
SMGL
but their activity or interest can change.
Our users certainly prefer active developers.
If the positions can increase the activity we could change them more often.
What about some "The most active developers" wiki page?

Imho we should give our users the vote too.
Some of them are more long term interest in SMGL as current developers.

> Nothing after that, and no interest in long term planning.

And who is more useful for SMGL? You or some developer with a long term
interest?
:-))

> Agreement from the developers that it is a good thing and necessary, could
> turn
> that "should" into a "must".

There is a problem. You can not give orders. SMGL is not their paid full time
job.

SMGL must be fun for them. We need more developers/active users.

> Let me know if I should change the roadmap to be version-number specific or
> change my scripts to use dates instead of release numbers.

Personally I prefer the dates, for example smgl-20040401.
I am aware of it is not so bombastic as smgl-1.0.
I really did not like the stress before our "1.0".
I do not want our team will be decimated because of some plans.

Have a nice ...
- lace -





Archive powered by MHonArc 2.6.24.

Top of Page