1
eric235u
is it time for a 'lead project manager'?
  • 2007/4/19 13:52

  • eric235u

  • Not too shy to talk

  • Posts: 149

  • Since: 2004/12/19


hi all. after listening to many complaints and looking around xoops, dev.xoops and sourceforge is seems clear that XOOPS as a community is in very bad shape from an administration standpoint. xoops.org and dev.xoops.org is in poor shape. our sourceforge page is empty except for the occasional spammer with almost zero cvs and svn activity. please see my latest post here.

i request that i be seriously considered for the post of 'lead project manager'. my goals would be purely administrative. to provide an environment for free software development to thrive. if i am not chosen for this position i highly suggest phppp and skalpa choose somebody to do this. XOOPS desperately needs an administrator and manager.

what does the community think?

thanks for your time.

2
mortuk
Re: is it time for a lead project manager?
  • 2007/4/19 13:58

  • mortuk

  • Not too shy to talk

  • Posts: 122

  • Since: 2005/12/13


Project manager: Skalpa

Do u mean webmasster? I think this iz coming with new site!

3
eric235u
Re: is it time for a lead project manager?
  • 2007/4/19 14:02

  • eric235u

  • Not too shy to talk

  • Posts: 149

  • Since: 2004/12/19


the problems are much more serious than a new website. the resources at sourceforge are not being utilized. the methodologies that make free software great are not being used. we are not getting new developers, we are losing them. proper management would fix this.

4
Dave_L
Re: is it time for a lead project manager?
  • 2007/4/19 14:36

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


I think XOOPS definitely needs improvement organization-wise.

skalpa and phpbb are very skilled at coding, but it doesn't make sense for them to have to use their valuable software development time designing/managing the XOOPS support sites and dealing with organizational issues.

Another job that I think would be useful is a Product Manager. XOOPS is, after all, a product, and IMHO, is not given enough focus in that respect.

5
carnuke
Re: is it time for a 'lead project manager'?
  • 2007/4/19 16:22

  • carnuke

  • Home away from home

  • Posts: 1955

  • Since: 2003/11/5


Quote:

eric235u wrote:
hi all. after listening to many complaints and looking around xoops, dev.xoops and sourceforge is seems clear that XOOPS as a community is in very bad shape from an administration standpoint. xoops.org and dev.xoops.org is in poor shape. our sourceforge page is empty except for the occasional spammer with almost zero cvs and svn activity. please see my latest post here.

i request that i be seriously considered for the post of 'lead project manager'. my goals would be purely administrative. to provide an environment for free software development to thrive. if i am not chosen for this position i highly suggest phppp and skalpa choose somebody to do this. XOOPS desperately needs an administrator and manager.

what does the community think?

thanks for your time.


This is exactly the kind of post that needs to be discussed, but NOT publically!
hhttp://houseofstrauss.co.uk Resource for alternative health and holistic lifestyle
search xoops

6
eric235u
Re: is it time for a 'lead project manager'?
  • 2007/4/19 16:31

  • eric235u

  • Not too shy to talk

  • Posts: 149

  • Since: 2004/12/19


who do you trust more, a governemnt that does business behind closed doors or a government that does business in public for all to see?

we can do everything in public, fix our problems and produce great free software.

7
gtop00
Re: is it time for a 'lead project manager'?
  • 2007/4/19 16:38

  • gtop00

  • Friend of XOOPS

  • Posts: 498

  • Since: 2004/11/13


Quote:

eric235u wrote:
who do you trust more, a governemnt that does business behind closed doors or a government that does business in public for all to see?


Dear Eric, a good goverment is a good coverment independently the way it does business. The question always is: is the goverment good for everybody?

Quote:
we can do everything in public, fix our problems and produce great free software.

Sounds like a product order. No, we cannot do everything in public.
Regarding XOOPS, we all have to "fix problems and produce great free software" not some 'goverment'.

8
eric235u
Re: is it time for a 'lead project manager'?
  • 2007/4/19 16:56

  • eric235u

  • Not too shy to talk

  • Posts: 149

  • Since: 2004/12/19


my government comment was merely an example. i personally have more confidence in individuals who speak openly and do not restrict speech. therefore i believe that XOOPS should be supportive of free software and free speech, as they are the same thing.

as a matter of fact, if we hid our conversations regarding security alerts and didn't allow dissenters to comment we would be... micro$oft! that is not my vision of the future of XOOPS. there are many great free software projects and we should follow their lead.

we can do everything in public! good work does not need to hide. public work encourages community confidence.

9
carnuke
Re: is it time for a 'lead project manager'?
  • 2007/4/19 17:18

  • carnuke

  • Home away from home

  • Posts: 1955

  • Since: 2003/11/5


Quote:
we can do everything in public! good work does not need to hide. public work encourages community confidence.


As you talk about this, I am beginning to understand more about what you mean. Good work does not need to hide. Agreed, but unfortunately, we have some hard talking to do, where the result will be good, but the process may be tough.

Put is this way: would you tell your wife/ husband that their underwear was showing in a crowded elevator?

No, you do it somewhere more discreetly to save them the embarrassment of others hearing or noticing.
hhttp://houseofstrauss.co.uk Resource for alternative health and holistic lifestyle
search xoops

10
Dave_L
Re: is it time for a 'lead project manager'?
  • 2007/4/19 17:34

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


The problem is deciding where to draw the line between private and public discussions.

I can think of a couple of situations where privacy is desirable:

1) Forum moderators discussing whether a user should be disciplined for his behavior. E.g., "Dave_L is causing a lot of trouble with his posting recently. Should we ban him?"

2) Initial posting of a software security issue. My preference would be to first notify a small group of qualified developers of the issue, so that they could quickly develop a patch or other stopgap measure. The issue, along with the corrective measure, would be posted publicly within a day or two, not hidden for months as is done in the case of proprietary software vendors.

But maybe eric is right, and even these types of issues should be public from the outset.

I think the XOOPS organization has gotten off-track by privatizing discussions that should be public, and making decisions that affect the direction of the project out of the sight of the community.

Login

Who's Online

296 user(s) are online (195 user(s) are browsing Support Forums)


Members: 0


Guests: 296


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits