do-windows team mailing list archive

["Krisztian Gyuris" <gyurisc@xxxxxxxxx>]

Can we use the bug management feature of launchpad?

On Thu, Jul 3, 2008 at 7:08 PM, Brian Pedersen <brian.pedersen@xxxxxxxxx>
wrote:

> Make that "task management features" in the first line of my previous post
> :)
>
> /Brian
>
> 2008/7/3 Brian Pedersen <brian.pedersen@xxxxxxxxx>:
>
> I have been looking at the track management features in launchpad, and it
>> seems everything that is not a bug is a blueprint.
>>
>> It also seems you can't register bugs and blueprints on a launchpad group,
>> you need a launchpad project.
>>
>> I have therefore started using the project that I made, for registering
>> the tasks previously discussed, let me know if you feel like they should be
>> moved somewhere else.
>>
>> https://blueprints.launchpad.net/windo
>>
>> You should have access to modify stuff there, else let me know.
>>
>> /Brian
>>
>>
>> 2008/7/3 Nick Parker <nickp@xxxxxxxxxxxxxxxxxx>:
>>
>> All,
>>>
>>> First off, great list to get things started Brian.  One thing I wanted to
>>> throw out is the 03 and 08 can somewhat happen in parallel with cooperation
>>> from the GnomeDo team.  As far as documentation goes, I am thinking that we
>>> can put some content up on a website (possibly using Launchpad again?) to
>>> benefit two distinct groups, end users and plugin developers.  The
>>> documentation can start to be formalized a little later on, once things
>>> stabilize enough.  Krisztian, looking forward to seeing what you've put
>>> together.
>>>
>>> Nick Parker
>>> www.developernotes.com
>>>
>>> On Thu, Jul 3, 2008 at 6:56 AM, Brian Pedersen <brian.pedersen@xxxxxxxxx>
>>> wrote:
>>>
>>>>
>>>> > I think launchpad has this facility, the bug tracker and blueprints
>>>> feature. I have no experience with those.
>>>> I will look into those this evening.
>>>>
>>>> > I already did this and I will check this in as soon as I am done with
>>>> 03.
>>>>  Great, cant wait to see those compile errors :)
>>>>
>>>> > I am almost there, I had to take out most of the UI code. I guess it
>>>> will be better to use Winforms and WPF for the Windows Version
>>>> I agree, at some stage we might consider introducing adapters, for now
>>>> lets just rock'n-roll
>>>>
>>>> > I would go for .NET 3.5 as the single requirement for the app. all
>>>> other dependencies would come with install. I would prefere to minimize the
>>>> amount of 3rd party libraries that comes with the install package.
>>>> We might benefit from being compatible with Mono, this could mean going
>>>> for .NET 2.0
>>>>
>>>> > We can set up a seperate web site for the windows version and host the
>>>> plugins there. Or we can introduce some ways of describing the plugin
>>>> platform
>>>> With binary compatibility as a goal, self-describing plugins would be
>>>> great.
>>>>
>>>> /Brian
>>>>
>>>>
>>>> 2008/7/3 Krisztian Gyuris <gyurisc@xxxxxxxxx>:
>>>>
>>>> Hello,
>>>>>
>>>>> I put my answers below. :)
>>>>> *01 - Find a task-/issue-/bug tracker*
>>>>> I think launchpad has this facility, the bug tracker and blueprints
>>>>> feature. I have no experience with those.
>>>>>
>>>>> *02 - Initial Visual Studio setup*
>>>>> I already did this and I will check this in as soon as I am done with
>>>>> 03.
>>>>>
>>>>> *03 - Move to a compileable state*
>>>>> I am almost there, I had to take out most of the UI code. I guess it
>>>>> will be better to use Winforms and WPF for the Windows Version
>>>>>
>>>>> *04 - Move to a launchable state (FFF)*
>>>>> *05 - Move to a base functional state (FFF)*
>>>>> *06 - Do a 0.1 alpha release*
>>>>> *07 - Get a single plugin to work*
>>>>> *08 - Reorganize/refactor modules to ease maintainance*
>>>>>
>>>>> *09 - Define platform requirements*
>>>>> I would go for .NET 3.5 as the single requirement for the app. all
>>>>> other dependencies would come with install. I would prefere to minimize the
>>>>> amount of 3rd party libraries that comes with the install package.
>>>>>
>>>>> *10 - Define plugin strategy*
>>>>> We can set up a seperate web site for the windows version and host the
>>>>> plugins there. Or we can introduce some ways of describing the plugin
>>>>> platform
>>>>>
>>>>> *11 - Port plugins*
>>>>>
>>>>> *12 - Define documentation strategy*
>>>>> Only install guide is ok, I think.
>>>>>
>>>>> *13 - Write documentation*
>>>>> We need a volunteer :)
>>>>>
>>>>> *14 - Define release plan*
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~do-windows<https://launchpad.net/%7Edo-windows>
>>>> Post to     : do-windows@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~do-windows<https://launchpad.net/%7Edo-windows>
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>