Re: [mylyn-dev] Workspace Provisioning with Mylyn

[Sebastian Schmidt <mail@xxxxxxxxxxxxxx>]

Hi Maarten,

ah ok. Something like a central PSF store?

I agree that this would help people kickstart development and there
are some questions in my survey to support your point. However, I
don't want to spread the results already after the first day ;)

What you would miss is the task context (in this case I don't mean
Mylyn context, but the broader context). So you would add pointers to
a git repository and most probably the master/head. Unless you ask
every project to maintain different profiles for all different task
categories, components, versions, and each and every combination of
them. The specific task however might still require a different
branch, maybe even a different set of repositories (depending on its
context). For example, you have ECF in your signature: some tasks
might require ECF repo at eclipse, some might require incubation repos
or ECF github repositories. Some a combination of them.

I still like the idea of making provisioning stuff available on a task
(readable, also for people without Mylyn). If you find some time,
checkout the stuff I posted on github (there's an update site too).
IMHO this project would make a good addition for the second step, that
is maintain and extend the information you provide with task context
and I'd be happy to contribute on that.

Cheers,

Sebastian


Am 23.03.2013 um 00:30 schrieb Maarten Meijer <mm105@xxxxxxxxx>:

> Hi,
>
> the idea was for the Eclipse projects to make the data available in some machine readable format, that can then processed into bugzilla, so task and task onboarding is in one place.
>
> Maarten
>
>
> On 22 mrt. 2013, at 20:14, Sebastian Schmidt <mail@xxxxxxxxxxxxxx> wrote:
>
>> Hi Maarten,
>>
>> Sounds interesting, thanks for the pointer.
>>
>> I'm not sure if someone would really fill in the information manually
>> for each bug (there are a lot of them). But since people already share
>> their context and the suggested approach would add the required
>> information to the context, it should be easy to parse an attached
>> context in bugzilla and use it to autofill your custom fields (for
>> people not using Mylyn). I actually like the idea a lot ;)
>>
>> Cheers,
>>
>> Sebastian
>>
>>
>>
>> Am 22.03.2013 um 12:54 schrieb Maarten Meijer <mm105@xxxxxxxxx>:
>>
>>> Hi Sebastian,
>>>
>>> Great plan!
>>>
>>> Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=397358 for mods requested to eclipse bugzilla to enable full use of this for better contributor & task onboarding experience. Maybe you can take this into account as well!
>>>
>>>
>>> Met vriendelijke groeten,
>>>
>>>
>>> Maarten Meijer
>>> mm105@xxxxxxxxx
>>> Eclipse RCP consultant & trainer
>>> contributed to Mylyn & ECF
>>>
>>>
>>>
>>> On 22 mrt. 2013, at 12:39, Sebastian Schmidt <mail@xxxxxxxxxxxxxx> wrote:
>>>
>>>> Hi,
>>>>
>>>> there are several discussions going on about how/if we could use Mylyn
>>>> context to store SCM configurations or similar task-related
>>>> information (e.g. [1], [2], [3]).
>>>>
>>>> The recurring idea behind these discussions seems to be that people
>>>> want to use the context to automate workspace provisioning (i.e.
>>>> developers joining in on a task should be able to automatically
>>>> checkout task-related scm repositories and branches, activate target
>>>> platforms, and start working right away).
>>>>
>>>> I tried to come up with a general framework for this and pushed it to
>>>> Github (under EPL):
>>>> https://github.com/sschmidt/edu.tum.cs.mylyn.provisioning
>>>>
>>>> The framework adds a new tab to the task editor which is automatically
>>>> filled with provisioning related information while you work on a task.
>>>> Currently, git repositories, target platforms and breakpoints are
>>>> supported. That is, we track which git repositories you use while
>>>> working on a task, which target platform is activated and which
>>>> breakpoints you use... and add it to the context. You can share the
>>>> workspace as used to and other developer can use it to checkout the
>>>> repositories, import the breakpoints or activate the appropriate
>>>> target platform.
>>>>
>>>> I'm also conducting a survey to learn more about requirements and
>>>> gather some feedback. Head over to:
>>>> https://www1.cs.tum.edu/survey/index.php/survey/index/sid/832249 for
>>>> that. Additionally, there's a giveaway among participants (it's a
>>>> bluetooth car which you can control with your favorite ios or android
>>>> device).
>>>>
>>>> Any feedback is highly appreciated ;)
>>>>
>>>> Cheers,
>>>>
>>>> Sebastian
>>>>
>>>>
>>>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=345661
>>>> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=384067
>>>> [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=378399
>>>> _______________________________________________
>>>> mylyn-dev mailing list
>>>> mylyn-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>>>
>>> _______________________________________________
>>> mylyn-dev mailing list
>>> mylyn-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>> _______________________________________________
>> mylyn-dev mailing list
>> mylyn-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev