[jitsi-dev] My Sunday Night Rant!


#1

I really hate trackers to begin with ... I hate how you need to go
through pages of inane details that don't really fit our project
structure anyway and how, while doing this you basically, as chef would
put it, "waiiit, and you wait, and you wait, and you wait ... and you
wait, and you wait, and you waiiiiiit ...."

As some of you know I'd much rather deal with shared todo lists but
that's another story.

Still, I can almost and very grudgingly accept that trackers are a
necessary evil. Just now however, I tried to enter a bunch of issues in
our JIRA and half of them appear with duplicate numbers. As a result
there's no way to edit half the issues because clicking on their link
sends you the wrong ticket.

And now I can't even show you the page with the query that shows the
issues, because of JIRA's preference not to use page specific URLs and
because all pages I see appear as
https://java.net/jira/secure/IssueNavigator.jspa

I am therefore attaching an image.

Maybe this is related to the recent update on java.net but it doesn't
really matter, I think we've had it with JIRA, so this is really to
announce that after we are done with the github migration we'll probably
setup a Trac of our own and migrate all tickets there.

Pavel is also almost done setting up a mailman instance for us, so we'll
drop SYMPA soon after.

Cheers,
Emil

···

--
https://jitsi.org


#2

Thats? intresting?
whenever i try to open that image in gwenview it crashes X! wtf?

- --
Yannik Völker


#3

Moving away from JIRA is so very welcome. Why not use GitHub issues? Is that not sufficient? It's nice and omits spreading over to yet another platform.

Best, steve

···

Am 22.04.2013 um 00:42 schrieb Emil Ivov <emcho@jitsi.org>:

I really hate trackers to begin with ... I hate how you need to go
through pages of inane details that don't really fit our project
structure anyway and how, while doing this you basically, as chef would
put it, "waiiit, and you wait, and you wait, and you wait ... and you
wait, and you wait, and you waiiiiiit ...."

As some of you know I'd much rather deal with shared todo lists but
that's another story.

Still, I can almost and very grudgingly accept that trackers are a
necessary evil. Just now however, I tried to enter a bunch of issues in
our JIRA and half of them appear with duplicate numbers. As a result
there's no way to edit half the issues because clicking on their link
sends you the wrong ticket.

And now I can't even show you the page with the query that shows the
issues, because of JIRA's preference not to use page specific URLs and
because all pages I see appear as
https://java.net/jira/secure/IssueNavigator.jspa

I am therefore attaching an image.

Maybe this is related to the recent update on java.net but it doesn't
really matter, I think we've had it with JIRA, so this is really to
announce that after we are done with the github migration we'll probably
setup a Trac of our own and migrate all tickets there.

Pavel is also almost done setting up a mailman instance for us, so we'll
drop SYMPA soon after.

Cheers,
Emil

--
https://jitsi.org
<Screen Shot 2013-04-22 at 00.34.45.png>


#4

So far, most jitsi dev opinions I've heard seem to be leaning toward
jetbrain's YouTrack.

The main advantage is that we will be able to track multiple projects
(videobrodge, libjitsk, jitsi for android and ice4j) within the same
environment.

Various levels of integration seem to be possible with github.

--sent from my mobile
Moving away from JIRA is so very welcome. Why not use GitHub issues? Is
that not sufficient? It's nice and omits spreading over to yet another
platform.

Best, steve

···

Am 22.04.2013 um 00:42 schrieb Emil Ivov <emcho@jitsi.org>:

I really hate trackers to begin with ... I hate how you need to go
through pages of inane details that don't really fit our project
structure anyway and how, while doing this you basically, as chef would
put it, "waiiit, and you wait, and you wait, and you wait ... and you
wait, and you wait, and you waiiiiiit ...."

As some of you know I'd much rather deal with shared todo lists but
that's another story.

Still, I can almost and very grudgingly accept that trackers are a
necessary evil. Just now however, I tried to enter a bunch of issues in
our JIRA and half of them appear with duplicate numbers. As a result
there's no way to edit half the issues because clicking on their link
sends you the wrong ticket.

And now I can't even show you the page with the query that shows the
issues, because of JIRA's preference not to use page specific URLs and
because all pages I see appear as
https://java.net/jira/secure/IssueNavigator.jspa

I am therefore attaching an image.

Maybe this is related to the recent update on java.net but it doesn't
really matter, I think we've had it with JIRA, so this is really to
announce that after we are done with the github migration we'll probably
setup a Trac of our own and migrate all tickets there.

Pavel is also almost done setting up a mailman instance for us, so we'll
drop SYMPA soon after.

Cheers,
Emil

--
https://jitsi.org
<Screen Shot 2013-04-22 at 00.34.45.png>


#5

Hm, well couldn't you just use the ticket system of the main entry on GitHub and simply use tags to differentiate the sub-projects? Or would that mean chaos since you then couldn't close open issues via commit notes?

···

Am 26.04.2013 um 12:17 schrieb Emil Ivov <emcho@jitsi.org>:

So far, most jitsi dev opinions I've heard seem to be leaning toward jetbrain's YouTrack.

The main advantage is that we will be able to track multiple projects (videobrodge, libjitsk, jitsi for android and ice4j) within the same environment.

Various levels of integration seem to be possible with github.

--sent from my mobile

Moving away from JIRA is so very welcome. Why not use GitHub issues? Is that not sufficient? It's nice and omits spreading over to yet another platform.

Best, steve

Am 22.04.2013 um 00:42 schrieb Emil Ivov <emcho@jitsi.org>:

> I really hate trackers to begin with ... I hate how you need to go
> through pages of inane details that don't really fit our project
> structure anyway and how, while doing this you basically, as chef would
> put it, "waiiit, and you wait, and you wait, and you wait ... and you
> wait, and you wait, and you waiiiiiit ...."
>
> As some of you know I'd much rather deal with shared todo lists but
> that's another story.
>
> Still, I can almost and very grudgingly accept that trackers are a
> necessary evil. Just now however, I tried to enter a bunch of issues in
> our JIRA and half of them appear with duplicate numbers. As a result
> there's no way to edit half the issues because clicking on their link
> sends you the wrong ticket.
>
> And now I can't even show you the page with the query that shows the
> issues, because of JIRA's preference not to use page specific URLs and
> because all pages I see appear as
> https://java.net/jira/secure/IssueNavigator.jspa
>
> I am therefore attaching an image.
>
> Maybe this is related to the recent update on java.net but it doesn't
> really matter, I think we've had it with JIRA, so this is really to
> announce that after we are done with the github migration we'll probably
> setup a Trac of our own and migrate all tickets there.
>
> Pavel is also almost done setting up a mailman instance for us, so we'll
> drop SYMPA soon after.
>
> Cheers,
> Emil
>
> --
> https://jitsi.org
> <Screen Shot 2013-04-22 at 00.34.45.png>


#6

Note that not all of these projects are on github.

Anyways, the feeling is that this would be suboptimal and that a youtrack
installation would work better .. We'll see. We'll probably give it a try
and reconsider if unhappy.

--sent from my mobile

···

On May 1, 2013 4:07 PM, "Steve" <stevebell@gulli.com> wrote:

Hm, well couldn't you just use the ticket system of the main entry on
GitHub and simply use tags to differentiate the sub-projects? Or would that
mean chaos since you then couldn't close open issues via commit notes?

Am 26.04.2013 um 12:17 schrieb Emil Ivov <emcho@jitsi.org>:

So far, most jitsi dev opinions I've heard seem to be leaning toward
jetbrain's YouTrack.

The main advantage is that we will be able to track multiple projects
(videobrodge, libjitsk, jitsi for android and ice4j) within the same
environment.

Various levels of integration seem to be possible with github.

--sent from my mobile
Moving away from JIRA is so very welcome. Why not use GitHub issues? Is
that not sufficient? It's nice and omits spreading over to yet another
platform.

Best, steve

Am 22.04.2013 um 00:42 schrieb Emil Ivov <emcho@jitsi.org>:

> I really hate trackers to begin with ... I hate how you need to go
> through pages of inane details that don't really fit our project
> structure anyway and how, while doing this you basically, as chef would
> put it, "waiiit, and you wait, and you wait, and you wait ... and you
> wait, and you wait, and you waiiiiiit ...."
>
> As some of you know I'd much rather deal with shared todo lists but
> that's another story.
>
> Still, I can almost and very grudgingly accept that trackers are a
> necessary evil. Just now however, I tried to enter a bunch of issues in
> our JIRA and half of them appear with duplicate numbers. As a result
> there's no way to edit half the issues because clicking on their link
> sends you the wrong ticket.
>
> And now I can't even show you the page with the query that shows the
> issues, because of JIRA's preference not to use page specific URLs and
> because all pages I see appear as
> https://java.net/jira/secure/IssueNavigator.jspa
>
> I am therefore attaching an image.
>
> Maybe this is related to the recent update on java.net but it doesn't
> really matter, I think we've had it with JIRA, so this is really to
> announce that after we are done with the github migration we'll probably
> setup a Trac of our own and migrate all tickets there.
>
> Pavel is also almost done setting up a mailman instance for us, so we'll
> drop SYMPA soon after.
>
> Cheers,
> Emil
>
> --
> https://jitsi.org
> <Screen Shot 2013-04-22 at 00.34.45.png>