Re: [Mantisbt-dev] Empowering the Mantis Community

[Rich <dvs...@gm...>]

>
> > We should write requirements for needed features even if there is
> > no developer or contributor that is ready to develop it.
> > Requirements are to capture the need and to make it easier to
> > implement such feature in the future.
>
> Document the requirements and features, even if your skills don't allow
> you to implement it. If I only wrote down things I knew I had the skills
> to implement in my projects, it wouldn't be where it is today. With
> other people outside the main "core team" looking at the code, playing
> with it, you'll have more luck adding new features you never considered
> before.
>
> > I would love to get your feedback on this.  Also please contact me if
> > you feel you can contribute in any of these areas.  My focus will be
> > to empower everyone who would like to contribute to Mantis to do so.
>
Agreed, With the wiki, nothing is permanent and documentation is
almost necessary to understand what features are and how to use them,
it took me months to start learning the parts of the code because the
docu-wiki was not very current.. I will make a point to start editing
the wiki.
> I should step up my involvement a bit again, but I've been buried with
> my "Normal Day Job(tm)" too, along with balancing my own OSS projects
> and release schedules.
>
...I have the same issue.
> I'll see what I can do. Maybe have a "Mantis Day", face-to-face event
> near or shortly following one of the popular Linux/OSS conferences so
> people can gain a better understanding of what it is, who is involved,
> how to contribute and so on. Just a thought.
>
> Whatever happened to Ken anyway?
>

I would love to participate in a "mantis day" I can try and get a
grant from local companies for a booth in one of the Linux expos. Any
idea what the cost might be for one say at the so-cal Linux expo?
>
Just my thoughts.

-- 
Rich