You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Vassil Dichev <vd...@apache.org> on 2009/01/17 22:14:19 UTC
Merge of hooks-actions branch
I've merged the hooks-actions branch to trunk last night and
documented it today here:
http://cwiki.apache.org/confluence/display/ESME/Actions
I took existing filters and actions from this document:
http://esmeproject.googlecode.com/files/actions.pdf
I intended to use the MoinMoin wiki.apache.org initially, so that
people without a submitted ICLA can contribute (e.g. Dick), but it
turns out we must request the creation of our own ESME space. It's
also an option for us to maintain our own wiki space, and I'm willing
to do it if we decide it makes sense (this also needs a request). OTOH
Bertrand mentioned that Sling are using a public Confluence wiki, so
it might not be required to have an ICLA to edit cwiki.apache.org
after all... I'm a bit confused at this point.
So, I'm done with major portions of 2 out of 3 of my Scrum tasks...
I'm cheating, of course, because this work was mostly ready before the
scrum started. Onto bug fixing and my third task now-
Twitter-compatible API for Twitter clients.
Have fun,
Vassil
AW: Merge of hooks-actions branch
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Latest version with actions from vassil is deployed on stax. First preliminary tests on the actions are promising. I've already created a tweet with an ESME action. That is sweet an ESME tweet
D.
-----Ursprüngliche Nachricht-----
Von: vdichev@gmail.com [mailto:vdichev@gmail.com] Im Auftrag von Vassil Dichev
Gesendet: Samstag, 17. Jänner 2009 22:14
An: esme-dev@incubator.apache.org
Betreff: Merge of hooks-actions branch
I've merged the hooks-actions branch to trunk last night and
documented it today here:
http://cwiki.apache.org/confluence/display/ESME/Actions
I took existing filters and actions from this document:
http://esmeproject.googlecode.com/files/actions.pdf
I intended to use the MoinMoin wiki.apache.org initially, so that
people without a submitted ICLA can contribute (e.g. Dick), but it
turns out we must request the creation of our own ESME space. It's
also an option for us to maintain our own wiki space, and I'm willing
to do it if we decide it makes sense (this also needs a request). OTOH
Bertrand mentioned that Sling are using a public Confluence wiki, so
it might not be required to have an ICLA to edit cwiki.apache.org
after all... I'm a bit confused at this point.
So, I'm done with major portions of 2 out of 3 of my Scrum tasks...
I'm cheating, of course, because this work was mostly ready before the
scrum started. Onto bug fixing and my third task now-
Twitter-compatible API for Twitter clients.
Have fun,
Vassil
AW: Why aren't all SVN commits in Jira?
Posted by "Hirsch, Richard" <ri...@siemens.com>.
OK. I think those committing code to SVN probably didn't know about using the JIRA issue id in their log messages.
Thanks.
D.
-----Ursprüngliche Nachricht-----
Von: bdelacretaz@gmail.com [mailto:bdelacretaz@gmail.com] Im Auftrag von Bertrand Delacretaz
Gesendet: Dienstag, 20. Jänner 2009 11:17
An: esme-dev@incubator.apache.org
Betreff: Re: Why aren't all SVN commits in Jira?
On Tue, Jan 20, 2009 at 11:02 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> There have been other subversion commits in the SVN trunk (for example,
> Vassil's actions, etc.) but they aren't visible in Jira
> (https://issues.apache.org/jira/browse/ESME?report=com.atlassian.jira.pl
> ugin.ext.subversion:subversion-project-tab). What do we have to do to
> make them appear in Jira as well?
The link to JIRA does seem to work, as you can see at
https://issues.apache.org/jira/browse/ESME-2 (use the "all" display
option), my http://svn.apache.org/viewvc?view=rev&revision=727325
commit is visible there.
Committers must be careful to start their svn log messages with the
JIRA issue id, like "ESME-2 - initial website..." in that example.
-Bertrand
Semantic Web and Microblogging: Plug-in candidate?
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I found an interesting project that uses semantic web technology on microblogging: sublog
s?Blog is an effort to combine ideas about microblogging, messaging and the sematic web into a practical tool ready for everyday work.
s?Blog listens for messages across standard internet protocols (e.g. XMPP, IMAP) and does useful things depending on the meaning of the messages it receives.
https://www.ohloh.net/p/sublog
This may sound similar to our action functionaliy but it is more based on semantic web technpology. This is a java-based project on Google Code (Apache 2.0 license) that might be a perfect candidate for a plug-in. It could be used to create new tags on messages that increase the ability of users to search and find information more effecienctly
I think @Daniel has already contacted the developer.
Thoughts?
D.
Re: Why aren't all SVN commits in Jira?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Jan 20, 2009 at 11:02 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> There have been other subversion commits in the SVN trunk (for example,
> Vassil's actions, etc.) but they aren't visible in Jira
> (https://issues.apache.org/jira/browse/ESME?report=com.atlassian.jira.pl
> ugin.ext.subversion:subversion-project-tab). What do we have to do to
> make them appear in Jira as well?
The link to JIRA does seem to work, as you can see at
https://issues.apache.org/jira/browse/ESME-2 (use the "all" display
option), my http://svn.apache.org/viewvc?view=rev&revision=727325
commit is visible there.
Committers must be careful to start their svn log messages with the
JIRA issue id, like "ESME-2 - initial website..." in that example.
-Bertrand
Why aren't all SVN commits in Jira?
Posted by "Hirsch, Richard" <ri...@siemens.com>.
There have been other subversion commits in the SVN trunk (for example,
Vassil's actions, etc.) but they aren't visible in Jira
(https://issues.apache.org/jira/browse/ESME?report=com.atlassian.jira.pl
ugin.ext.subversion:subversion-project-tab). What do we have to do to
make them appear in Jira as well?
D.
Re: Added all items from scrum meeting for first sprint to Jira
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Jan 20, 2009 at 10:07 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> I think vdichev and dpp should have the rights as well.
Added both as committers in JIRA.
-Bertrand
AW: Added all items from scrum meeting for first sprint to Jira
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I think vdichev and dpp should have the rights as well.
Thanks.
D.
-----Ursprüngliche Nachricht-----
Von: bdelacretaz@gmail.com [mailto:bdelacretaz@gmail.com] Im Auftrag von Bertrand Delacretaz
Gesendet: Dienstag, 20. Jänner 2009 09:53
An: esme-dev@incubator.apache.org
Betreff: Re: Added all items from scrum meeting for first sprint to Jira
On Tue, Jan 20, 2009 at 9:16 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> I've added the items from our first scrum meeting to the apache jira:
> https://issues.apache.org/jira/secure/BrowseProject.jspa...
Cool! That'll help people keep track of what's happening.
> ...Jira for ESME still really isn't configured correctly. We have no
> components and no available versions. Maybe, a committer can add these
> values....
JIRA users dhague and dkulp should be allowed to create components and
versions, if not let me know.
Same if other committers need these rights, indicate JIRA username in that case.
-Bertrand
Re: Added all items from scrum meeting for first sprint to Jira
Posted by Vassil Dichev <vd...@gmail.com>.
> Same if other committers need these rights, indicate JIRA username in that case.
I can't seem to assign issues to me, whom should I turn to?
Re: Added all items from scrum meeting for first sprint to Jira
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Jan 20, 2009 at 9:16 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> I've added the items from our first scrum meeting to the apache jira:
> https://issues.apache.org/jira/secure/BrowseProject.jspa...
Cool! That'll help people keep track of what's happening.
> ...Jira for ESME still really isn't configured correctly. We have no
> components and no available versions. Maybe, a committer can add these
> values....
JIRA users dhague and dkulp should be allowed to create components and
versions, if not let me know.
Same if other committers need these rights, indicate JIRA username in that case.
-Bertrand
Added all items from scrum meeting for first sprint to Jira
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I've added the items from our first scrum meeting to the apache jira:
https://issues.apache.org/jira/secure/BrowseProject.jspa. Please look
at the tasks and provide comments if necessary.
Jira for ESME still really isn't configured correctly. We have no
components and no available versions. Maybe, a committer can add these
values.
I still have to look at the old items from the Google site and add the
relevant ones here as well.
D.