RE: [mylar-dev] Re: Bugzilla Repository cannot be added

["Mik Kersten" <beatmik@xxxxxxx>]

Eugene,

There is definitely a potential for some interesting integration here, and
it's very cool that you prototyped it within a couple of days of my musing
about it :)

I wonder whether to really work it would need to be tied in to an integrated
tool that allows reading/authoring of those messages?  Without that if my
personal preference as a user might be to have a repository task that has a
URL link to the corresponding email message, since they're easy to link on
eclipse.org (and maybe some UI sugar for creating reports from news/mail
messages).  Which reminds, me, if a bug report does have a URL property set
we could add a separate browser tab for viewing it that message.  But
obviously that wouldn't give the benefit of grouping by thread within the
list, etc.

Regarding incorporating this into Mylar, what is the exact list of
dependencies and licenses?  Each would require an EMO review, and as far as
I know impossible for us to add GPL dependencies or any other non-EPL
compatible ones.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Monday, March 06, 2006 2:28 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Re: Bugzilla Repository cannot be added
> 
> Mik Kersten wrote:
> 
> > That is very cool Eugene!
> 
>    Thanks Mik. I hope we could find a way to somehow integrate that into
> Mylar core.
> 
> > Could you describe an example work flow for using this?  What kind of
> > news posts/mail/RSS would you like to have a context for?
> 
>    Hey, do your own work for that PhD. thesises of yours. Just kidding. :-
> )
> 
>    I think usecases for email/news are quite obvious. It will be very
> handy when working with mail lists, newsgroups of support forums when
> users could ask all kind of questions about product. So, you could
> activate task and look trough the code before replying. Then you could
> even attach task context to the response. Also, such provider may group
> messages by conversation within single task.
> 
>    Speaking about RSS, there are issue tracking systems that only
> provide an rss api. Eg. http://springide.org/project/report/1
> 
>    Also, lot of web based forum implementations have built-in rss support.
> 
>    regards,
>    Eugene
> 
> 
> >     --------------------------------------------------------------------
> ----
> >
> >     *From:* mylar-dev-bounces@xxxxxxxxxxx
> >     [mailto:mylar-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Eugene
> Kuleshov
> >     *Sent:* March 5, 2006 4:04 AM
> >     *Cc:* Mylar developer discussions
> >     *Subject:* [mylar-dev] Re: Bugzilla Repository cannot be added
> >
> >
> >       As promised. Here is a screenshot of the quick and dirty
> >     JavaMail-based repository connector supporting pop3, imap and nntp
> >     (including auth and crypto).
> >
> >
> >
> >       Most of the time I spent on building gnu JavaMail provider with
> >     nntp support and removing some usage of the URL class in Mylar code.
> >
> >       I guess there will be some licensing issues with gnu packages, so
> >     as last resort it is probably possible to use Jakarta net component
> >     for nntp (non JavaMail API though) and Sun's JavaMail jars for pop3
> >     and imap.
> >
> >       regards,
> >       Eugene
> >
> >
> >     Eugene Kuleshov wrote:
> >
> >>     P.S. Since posts like this involve investigation, I think I need
> >>     task contexts to start working with newsgroup posts in addition to
> >>     bug reports ;)
> >>
> >       That is easy. Using Javamail it would be pretty much the same code
> >     for pop3, imap or nntp. So, as soon as you confirm that API is
> >     stable...
> >
> >       regards
> >       Eugene
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev