Re: [libreoffice-website] [Drupal Website] Reminder note re: Developing and coding

Marc,
I disagree with Michael's assessment that the code development team has been
overlooked. There already is a placeholder for the code development team
under the 'contribute' heading. I have been following discussions about bugs
and development over the past couple of weeks, and there doesn't seem to be
a consensus yet about the structure and requirements for the code dev team.

Is there any need to raise the code dev team above all others within the
community, as is being suggested? Would having a link on the main product
information page to code development really bring about more code being
created compared to the team page being located inside the normal community
structure?

Personally, I think that anybody who has the skill set and the motivation to
contribute will be actively looking to contribute rather than stumbling
across the code dev page and then deciding to contribute.
In addition to this I would prefer to see a flatter community structure to
encourage equality amongst opinions, decisions and proposals. ie. I would
like to leave the Code Dev team page in the existing community structure
rather than breaking it out.

What are people's thoughts?

Michael Wheatland

On Wed, Nov 17, 2010 at 8:16 PM, Marc Paré <marc@marcpare.com> wrote:

> Just a good reminder from Michael Meeks
>
> ============
>
> >       Looks interesting. However - I'm slightly worried that 'Develop' is
> no
> > longer a top-level item. We -really- want to continue to encourage more
> > and more people to get involved developing the product, and in
> > particular diving into the code and helping to clean it up.
> >
> >       As such, I'd -really- love to stick with a top-level, one-click
> > "Develop" top-level, that will take people to a page showing them how to
> > get the code, and get involved hacking :-)
> >
> >       HTH,
> >
> >               Michael.
>
> ============
>
> I think that Michael raises a good point. Let's not forget the whole aspect
> of developing, hacking code of the project. We do want to interest more
> coders to join the project as well as encourage members to report bugs as
> well as encourage those who can code/hack to help fix/improve templates etc.
> where they can. This whole aspect of the project may have been forgotten by
> some of us on the Drupal Website Team.
>
> Maybe a porthole to a Dev page (Devs' hub page) from where devs can travel
> to different parts of the project but from a coders perspective and needs?
> We need to keep their needs in mind too.
>
> Marc
>
>
> --
> E-mail to website+help@libreoffice.org <website%2Bhelp@libreoffice.org>for instructions on how to 
> unsubscribe
> List archives are available at http://www.libreoffice.org/lists/website/
> All messages you send to this list will be publicly archived and cannot be
> deleted

--
E-mail to website+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/website/
All messages you send to this list will be publicly archived and cannot be deleted