From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-jira.el... and Org conventions (Bastien, Carsten and all)
Date: Tue, 03 Jan 2012 17:25:39 +0100 [thread overview]
Message-ID: <80hb0cvjlo.fsf@somewhere.org> (raw)
In-Reply-To: 85obuk4wax.fsf@gmail.com
Hi Bao,
"Bao Haojun" wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> "Bao Haojun" wrote:
>>> I have implemented org-jira.el, bringing org-mode and Jira system
>>> together.
>>>
>>> Wrote a Wiki page for it on emacswiki:
>>> http://www.emacswiki.org/emacs/OrgJiraMode
>>>
>>> Hope somebody find it useful, if he/she is also using Jira and loves
>>> org-mode.
>>
>> I had never heard of Jira, but your work definitely looks very promising.
>> IMHO, it should be compared with org-x and its extension to Redmine, among
>> others.
>
> Thanks for the praise! Jira is a "commercial" issue tracker, but it also
> seems to be OSS friendly (by allowing OSS community to use the software for
> free; Apache is using it, see http://wiki.apache.org/general/ApacheJira).
>
> Likewise I had not heard of org-x and Redmine, thanks for letting me know.
>
>> But this triggers, for me, another "concern" which is the very wide variety
>> of ways to define the same thing.
>>
>> So, my point is: wouldn't it be better if we proposed standard properties
>> in Org (in the manual), and implemented mappings in the Org "integration"
>> packages (org-jira, org-taskjuggler, org-redmine and the like)?
>>
>> So, say for example that, from now on, it's more standard in Org to use
>> "Assignee" (or anything else) for representing who's assigned a task, and
>> have every package map the property "Assignee" to whatever keyword used in
>> external tools for representing that concept?
>
> I can see your point, that standard thing is good, if it's already here, I
> will definitely try comply to them.
Thanks for your proposition.
I will let others express their own meaning, but, seeing your answer, I wanted
to recalibrate what I expressed.
> But your worrying people need to transition from one system such as org-jira
> to another such as org-x, I think they are not very often. Because if it
> happens, it would mean that the COMPANY/COMMUNITY has decided to switch from
> Jira to Redmine, can you imagine how often that can be?
>
> Besides, even if that really happens, it would also mean the
> COMPANY/COMMUNITY has got a way to transition from Jira to Redmine, so there
> would have already been a way to transit from org-jira to org-x: org-jira ->
> Jira -> Redmine -> org-x (and vice versa).
>
> So my point is, if someone try to make transition easy, they should do it on
> the company level, such as from Jira to Redmine. Org mode feels kind of
> personal to me, and I feel good enough to be able to sync between company
> issue tracking system and my org-mode, no need for it to be able to transit
> to another issue tracking system's org-mode.
You're right we could understand my proposition as being an easier way to
change between bug tracking systems. But not only that.
I gave the example of Task Juggler: wouldn't it be nice to be able -- at any
point in time -- to generate a dependency graph through Task Juggler, while
being able (at the same time, without touching anything) to get the tasks
maintained in, let's say, Redmine (which does not offer a Gantt chart
functionality IIRC)?
So, the question is not really about switching from one system to another, but
more about using 2 (or more) systems in parallel... While the former may be a
rare occurrence in a project, I guess the latter is more a common wish.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-01-03 16:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 12:08 org-jira.el Bao Haojun
2012-01-03 8:07 ` org-jira.el... and Org conventions (Bastien, Carsten and all) Sebastien Vauban
2012-01-03 15:53 ` Bao Haojun
2012-01-03 16:25 ` Sebastien Vauban [this message]
2012-01-03 16:28 ` Allen S. Rout
2012-01-04 16:47 ` Bastien
2012-01-04 17:13 ` Nick Dokos
2012-01-03 23:34 ` Standard property proposal (was: org-jira.el... and Org conventions (Bastien, Carsten and all)) Karl Voit
2012-01-04 16:50 ` Standard property proposal Bastien
2012-01-03 13:49 ` org-jira.el Marc Spitzer
2012-01-04 16:52 ` org-jira.el Bastien
2012-01-04 17:53 ` org-jira.el Nick Dokos
2012-01-05 10:00 ` org-jira.el Bastien
2012-01-05 14:42 ` org-jira.el Bao Haojun
2012-01-05 17:08 ` org-jira.el Jonathan Arkell
2012-01-06 0:32 ` org-jira.el Bao Haojun
2012-01-06 15:24 ` org-jira.el Bao Haojun
2012-01-04 18:36 ` org-jira.el Richard Riley
2012-01-04 19:49 ` org-jira.el Mehul Sanghvi
2012-01-05 10:01 ` org-jira.el Bastien
2012-01-05 15:42 ` org-jira.el OSiUX
2012-01-06 0:28 ` org-jira.el Bao Haojun
2012-01-06 15:54 ` org-jira.el Bao Haojun
2012-01-09 20:26 ` org-jira.el OSiUX
2012-01-10 2:40 ` org-jira.el Bao Haojun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80hb0cvjlo.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).