Hi,
it looks like I can't assign issues for the clerezza project on Jira.
Could someone with the needed rights include my Jira account (enridaga)
within the Clerezza contributors?

Thank you!
Enrico



On 5 September 2013 13:01, enridaga <[email protected]> wrote:

> Hi Reto,
>
>
> On 3 September 2013 15:55, Reto Bachmann-Gmür <[email protected]> wrote:
>
>> Hi Enrico
>>
>> Sound good to me. Not sure when git will be ready so I'm not sure if its
>> worth waiting till this is available before creating a branch.
>>
>> As long as virtuoso isn't part of the reactor see alos no problem having
>> this in trunk right away and add it to the reactor when this is ready.
>>
> Ok, so I will commit it to trunk as it is, to don't interfere with the
> git-migration task.
> I created CLEREZZA-810  .
>
> Cheers,
> Enrico
>
>
>> In general I would like to have a bit deeper directory structure in
>> clerezza. At least have an rdf and a platform directory grouping these
>> projects. But that's another story.
>>
>> Cheers,
>> Reto
>>
>>
>> On Mon, Sep 2, 2013 at 2:04 PM, enridaga <[email protected]> wrote:
>>
>> > Hi all,
>> >
>> > as agreed, I am going to donate the code at [1] to the project.
>> > I recently fixed dependency versions so now it compiles with the
>> clerezza
>> > latest trunk.
>> > My plan is to
>> > 1) open a jira issue about it
>> > 2) commit the whole project to a branch named clerezza-virtuoso
>> > 3) do some refactoring of poms and, as soon as it compiles, move the two
>> > subprojects to trunk
>> >
>> > WDYT?
>> >
>> >
>> > Enrico
>> >
>> >
>> > [1] https://github.com/enridaga/clerezza-virtuoso
>> >
>> > --
>> >
>> >
>> ------------------------------------------------------------------------------
>> > enridaga
>> >
>>
>
>
>
> --
>
> ------------------------------------------------------------------------------
> enridaga
>



-- 
------------------------------------------------------------------------------
enridaga

Reply via email to