elementary-dev-community team mailing list archive

[Allen Lowe <lallenlowe@xxxxxxxxx>]

Should we just create a Launchpad project for it and have people file
bugs about the guide?

Allen Lowe

On Sat, Feb 18, 2012 at 4:41 AM, Сергей <shnatsel@xxxxxxxxx> wrote:
> Hey guys,
>
> You all probably know about elementary developer guide that has been in
> drafting for quite a while already. The current draft can be viewed at
> http://tiny.cc/dev-guide-draft and the remaining work items are listed in
> the blueprint:
> https://blueprints.launchpad.net/elementaryweb/+spec/developer-guide
>
> This guide is already a truly epic collaborative work, but, as the blueprint
> whiteboard states, there's always room for improvement. But I think we've
> reached the point where we, as devs who already know the processes, make too
> much assumptions about what new devs need. In other words, the guide needs
> user testing.
>
> So I propose releasing a beta of the guide. With commenting open for
> everybody, an intro to commenting on gdocs in the journal article (not very
> discoverable feature), and a huge BETA label.
>
> I've finished Bazaar setup walkthrough today. Here is a list of things left
> be done before releasing a beta:
>
> Add links to coding style (it's gone from the doc! Where is it?)
> Get rid of using statements in code samples, to conform the coding style
> Add build environment setup guide - Granite had a release recently, right? I
> should move it to testing or stable then...
> Looks like that's it for now.
>
> --
> shnatsel
>
> P.S. props and kudos to the guy who added those tips with "info" icon, it
> makes the guide much easier to navigate and read.
> --
> Mailing list: https://launchpad.net/~elementary-dev-community
> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~elementary-dev-community
> More help   : https://help.launchpad.net/ListHelp
>