openshot.developers team mailing list archive

["eolinwen@xxxxxxxxx" <eolinwen@xxxxxxxxx>]

>>In terms of future plans, I recently just saw that the OpenShot video
editing library is being developed. When OpenShot 2.0 comes out, the older
bugs that affected the MLT version of OpenShot will need to be handled.
Maybe mark them as invalid or wont fix?

Oh I see that you are aware. It was what I was thinking when I have seen the
tag mlt and all the bugs concerning.
For me invalid is more appropriated.

Thanks a lot for your active participation. :)

2011/6/16 John Volk <poweruser32@xxxxxxxxx>

> **
> Thank you Olivier,
>     In terms of future plans, I recently just saw that the OpenShot video
> editing library is being developed. When OpenShot 2.0 comes out, the older
> bugs that affected the MLT version of OpenShot will need to be handled.
> Maybe mark them as invalid or wont fix?
>
> Oh and regarding my last email to Andy, I think it would be better to
> confirm all the wishlist bugs but then triage the ones that we want to work
> on. I just don't want wishlist bugs to have the undecided status.
>
> Thanks,
> John
>
>
> On 6/16/2011 9:13 AM, eolinwen@xxxxxxxxx wrote:
>
> Hi John,
>
> Welcome among us.
>
> You help is welcome also in this moment.
> And thanks a lot for the explanations, that's right that we have not a good
> utilisation of our management 's bugs plateform.
> Your cleaning is falling down at the good period with our future plans.
> Like this, we will have a better management/view of the bugs, wishlist,
> Question,...
>
> Oh I should introduce me : I am Olivier Girard (french) that you know me
> better as Cenwen.
>
> Best regards.
>
> 2011/6/16 John Volk <poweruser32@xxxxxxxxx>
>
>> Hello all OpenShot Developer,
>>    I would like to introduce myself to the team. My name is John Volk, I
>> do not know how to program but would like to help with the bug management of
>> OpenShot. I'm sorry for all the bug mail going to the whole team, but I'm
>> still trying to familiarize myself with the guidelines for triaging bugs.
>> From what I can tell most of you are developers actually working on code,
>> but I think it is still crucial for you guys to know whats going on. Well
>> here are the things that Johnathan would liked worked on in terms of bugs.
>>
>>
>>>    - *Duplicates* - I still think we have lot of duplicate reports that
>>>    need to be consolidated.  The trick is to find the best bug report to link
>>>    all the duplicates to.
>>>    - *Remove* the "wishlist" tag.
>>>    - *MLT Related Crashes* - I would love to somehow separate all the
>>>    MLT related issues, including segmentation faults, flashes of white, video
>>>    decoding issues, etc...  Maybe we could use an "mlt" tag, or something
>>>    similar.  It is my belief that most of our bugs are related to MLT rather
>>>    than OpenShot, so once they have all been identified.... the next step is to
>>>    mark them as "invalid" or assign them to the "MLT" launchpad project
>>>    instead.  However, let's not pull the trigger on closing or moving these bug
>>>    reports quite yet.  But eventually, I would like them to disappear from our
>>>    bug list.
>>>    - *Incompletes* - Many reports just don't have enough info to
>>>    reproduce the issue, or they are just vague "something broke" reports.  I
>>>    would love to mark all of these bugs as "incomplete"
>>>
>>>
>>  It is also very important that everyone is consistent when organizing
>> bugs. I am trying to follow https://wiki.ubuntu.com/Bugs/HowToTriage as
>> best as possible. I will summarize below.
>>
>>
>>    - *Wishlist - *When the importance is set to wishlist, set the status
>>    to* Triaged*.
>>    - *Patch - *When ever you add a patch to a bug mark the attachment as
>>    a patch and add the patch tag. This is what the triage guide says to do, but
>>    I do not know if the tag is necessarily. Any thoughts? (I wouldn't mind
>>    deleting it)
>>    - *Importance - *The importance needs to always be set. The default is
>>    medium. see https://wiki.ubuntu.com/Bugs/Importance for more details.
>>    - *Confirmed - *The status should be set to confirmed when the bug is
>>    affecting more than one person. If you (not the bug reporter) can reproduce
>>    the bug it can also be marked as confirmed.
>>    - *Triaged - *The status should be set triaged when a bug can be
>>    confirmed and is ready to be worked on by a developer. see
>>    https://wiki.ubuntu.com/Bugs/Improving
>>    - *Incomplete - *Not enough information.
>>
>> One thing that needs to be worked on is setting more bugs to triaged.
>> Yesterday there was only one or two bug triaged. The whole wishlist is
>> triaged now too.
>>  This is what I am trying to follow, but if OpenShot already follows a
>> different system, please let me know. I am looking forward to working with
>> you all.
>>
>>  BTW During most of the summer starting tomorrow night, I will only be
>> able to be at a computer on Saturday nights.
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openshot.developers
>> Post to     : openshot.developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openshot.developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Olivier
> Cenwen un elfe sur la banquise/ an elve on the ice
> Mon blog perso  sur le multimédia, Ubuntu, Linux et OpenShot :
> http://linuxevolution.wordpress.com/
> Le forum d'Openshot où vous me trouverez : http://openshotusers.com/
> http://openshotusers.com/forum/index.php
>
>
>


-- 
Olivier
Cenwen un elfe sur la banquise/ an elve on the ice
Mon blog perso  sur le multimédia, Ubuntu, Linux et OpenShot :
http://linuxevolution.wordpress.com/
Le forum d'Openshot où vous me trouverez : http://openshotusers.com/
http://openshotusers.com/forum/index.php