Received: by 10.52.100.3 with SMTP id eu3mr8388vdb.0.1349526077631;
Sat, 06 Oct 2012 05:21:17 -0700 (PDT)
X-BeenThere: joomlabugsquad@googlegroups.com
Received: by 10.220.226.7 with SMTP id iu7ls1958161vcb.6.gmail; Sat, 06 Oct
2012 05:21:16 -0700 (PDT)
Received: by 10.52.175.5 with SMTP id bw5mr2084819vdc.16.1349526076426;
Sat, 06 Oct 2012 05:21:16 -0700 (PDT)
Date: Sat, 6 Oct 2012 05:21:15 -0700 (PDT)
From: Kevin <i...@weblinksonline.co.uk>
To: joomlabugsquad@googlegroups.com
Message-Id: <ecdd54de-6b70-4b8e-8d30-a565ee1815cb@googlegroups.com>
In-Reply-To: <8326f785-7d4e-44b5-bf51-278ca7276469@googlegroups.com>
References: <66bfd1b3-02cf-47b1-8906-f98f0b756fda@googlegroups.com> <CANdmvYs1T+Yo4eq8mFgOw4+pBGpG0zW9rHKqfktLxFk_cS9cgA@mail.gmail.com>
<CABYB9+CgVM6iM5mdJ-eaD+SWCfFjHWfcSBqj9rBwtGh3fKbv-Q@mail.gmail.com>
<96d7c0c1-0f30-4a37-ba77-1407f2b92f1c@googlegroups.com>
<88d2e37a-b1e2-4549-8a22-6329383d9c10@googlegroups.com>
<02af9f56-2dd4-4ae8-a7f4-eae6f187ad83@googlegroups.com>
<c5af3a27-8728-4476-b0e0-46e4e9fa1741@googlegroups.com>
<57c43fb6-1563-4260-b3cc-7bec18148fe0@googlegroups.com>
<af412d9c-b63f-4c3e-a812-7561e8da5532@googlegroups.com>
<8326f785-7d4e-44b5-bf51-278ca7276469@googlegroups.com>
Subject: Re: [jbs] Colors on status in Joomlacode bug tracker
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_166_17793465.1349526075942"
------=_Part_166_17793465.1349526075942
Content-Type: multipart/alternative;
boundary="----=_Part_167_17668410.1349526075942"
------=_Part_167_17668410.1349526075942
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
"I don't see what commenting and installing software have to do with each
other"
What is the url for Git that has a list of all the Joomla pull requests so
that a non dev can decide which bug they can test/comment on ?
Where is the url for the list on Git where non devs can report bugs ?
"In github you can also make a patch+ issue a pull request right on the web"
Now either I missed that or it has never been stated before. All the
tutorials I have seen links to have required syncing the computer with
Git(in some way or other.)
Link to a tutorial on how to do pull requests on the web would be good
thanks. Because every thing I've looked at requires all sorts of
configuration before a patch can be applied.
For the umpteenth time testing a Git patch is more complex(initially) than
testing an SVN patch. With svn install one piece of software, point it at
the svn trunk put in user pass ... done. Download the patch right click
... done. But with Git download the software configure to sync with Git
and a load of other things ... because the software that is used to test a
Git patch will not work unless you have the whole caboose.
btw Tortoisesvn will download the 2.5 git branch to the computer but not
the trunk.
On Saturday, 6 October 2012 01:58:22 UTC+1, Elin wrote:
>
> For both github and joomlacode forum users have to register a new account
> and learn how to report.
>
> I don't see what commenting and installing software have to do with each
> other. If you want to make a comment use the web ui to make a comment.
> That's exactly the same in both.
>
> Unlike gForge, Git hub does not have a built in form building UI for
> administrators so it loses in the ability to ask or even require reporters
> to provide crucial information like cms version, php version. database and
> browser. Also github does not have duplicate tracking or a way to upload
> files. It also does not have query building/saving and downloading to csv
> or xls. So advantage gForge for those items.
>
> In github you can also make a patch+ issue a pull request right on the
> web. I've gotten dozens of people to make contributions by saying just go
> to the file, click edit, make the change and click save. So for beginners
> with simple change proposals github wins hands down. You don't even have to
> learn to work with a diff file. There is no equivalent of that in
> gforge+svn. Adantage github.
>
> So for people reporting issues and making simple suggested changes in
> code, things are either equivalent or slightly to the advantage of github.
>
> For people who want to test I really think it depends on what process you
> use. For me, pulling a patch from github or from joomlacode is the same. I
> apply patches in the same way and test in the same way. I keep one messy
> branch where I apply maybe a dozen jbs patches and then periodically, when
> they are going to interfere with each other, I reset the whole thing.
> That's exactly what I did in svn except it was one checkout. For both svn
> and git I installed software to help me manage things.
>
> For people who want to write code, I think at this point the consensus
> seems to be that github is easier and more encouraging of collaboration.
>
> The real issue I care personally about in a self-interested way is which
> system makes it easiest to manage a tracker with typically 400-600 open
> issues and, in fact, a number of separate things i.e. a 2.5 tracker, a
> trunk tracker, a feature tracker, and a security tracker, and a number of
> trackers with historical function, plus a large number of people working in
> different places. Which lets me keep the most open issues in my working
> memory and which makes it easiest to find an old issue when I think "I know
> I have seen that issue before"? Also what system is JM going to complain
> about least :P. For the latter I'd strongly like an open source solution
> since the main problem with both options we have been discussing is that
> the only work we can do to make it work the way we want is to use apis.
> From what I have seen the github apis are much easier to work with.
>
> Elin
>
>
>
> On Friday, October 5, 2012 7:06:05 PM UTC-4, Kevin wrote:
>>
>> "*While people sending code can easily indicate which branch the code is
>>> for, people making issue reports don't have an easy way to mark that
>>> (because even if jbs can apply tags new reporters won't have access to the
>>> tagging"*
>>>
>> That is exactly what I meant when I said
>>
>>> "*But could everyone in bugsquad comment inGit Without having to
>>> install and configure software*"
>>>
>>
>> Yes there are pitfalls with Joomlacode tracker but to "*Or drop
>> Joomlacode and svn completely and just use the built in functionality of
>> github :)*" ... might have more pitfalls. After all if a user in the
>> forums reports a bug then ... with the current system in Joomlacode ... it
>> is a simple mater to report the bug after testing. And I have even managed
>> to test a few simple patches as well.
>>
>> I enjoy helping out in bugsquad but feel that it could easy to fall
>> behind with too many changes. And wonder how many other non-developers
>> could get left behind as well? Not trying to be obstructive of improvement
>> ... just putting a point of view that *"Or drop Joomlacode and svn
>> completely and just use the built in functionality of github :)"* may
>> not be a change for the best. And explaining my thought process for why
>> not.
>>
>>
>> On Friday, 5 October 2012 23:43:42 UTC+1, Elin wrote:
>>>
>>> https://github.com/joomla/joomla-cms/issues
>>> Just comment and say what version and if you are making a pull request
>>> specify the correct target branch (master for J3, 2.5 for 2.5). But that
>>> is a great example of why the github tracker is not really workable without
>>> help. While people sending code can easily indicate which branch the code
>>> is for, people making issue reports don't have an easy way to mark that
>>> (because even if jbs can apply tags new reporters won't have access to the
>>> tagging plus they won't realize that it's needed just like on any other web
>>> UI people will not read instructions that you can be sure of).
>>>
>>> I don't understand the "you:" in your comment .. the whole point is we
>>> want to keep what we have which is close to 100 people able to change
>>> statuses. I also have no idea what 'devs' you are talking about but I'm
>>> pretty sure Mark and JM want more help not less. What we need is a solution
>>> that maps well to the current processes that we have and are satisfied with
>>> and that as much as possible fixes the ones that we aren't. The way the
>>> JBS works is pretty unusual and that has made finding a product that maps
>>> well to it difficult. We don't want JBS to have to fit a tracker we want a
>>> tracker to have to fit JBS.
>>>
>>>
>>> Currently we have about 609 issues with some kind of open status on the
>>> main tracker on joomlacode.
>>> https://github.com/popular/starred on that list I think Rails is the
>>> only one that comes close to that although it's confusing where their
>>> numbers are coming from.
>>>
>>> Elin
>>>
>>> On Friday, October 5, 2012 11:40:12 AM UTC-4, Kevin wrote:
>>>>
>>>> @Elin
>>>>
>>>> What is the url on Git for the comments on J3 and where is the url for
>>>> the comments on 2,5 ? All I can see is lots of individual discussions on
>>>> each individual pull request page. At least with Joomla code there is only
>>>> 1 url for each version of Joomla.
>>>>
>>>> " *is not currently adequate for managing close to 100 people with
>>>> status changing privileges*"
>>>> That can get complicated but if you want to limit it to just the Dev's
>>>> being able to do that ... then fine no problem with that. More work for
>>>> the Devs and less work for the Testers/ticket handlers.
>>>>
>>>> "*Even in the comparatively slow low volume platform tracker you see
>>>> that once it's above 100 open issues it's really kind of a pain and that
>>>> when people make a report and disappear the reports tend to just fade away
>>>> rather then have someone else step in and fix*"
>>>> Yes, but is that not true about any list with 100+ entries, no matter
>>>> where the list is ?
>>>>
>>>>
>>>>
>>>> On Friday, 5 October 2012 12:51:24 UTC+1, Elin wrote:
>>>>>
>>>>> @Kevin I'm not sure what you mean, any one can comment on any issue in
>>>>> github, you just need to login and you can put both attached comments and
>>>>> inline comments. I do think that there will be an issue when people need to
>>>>> make pull requests against both the 2.5 branch and against master or just
>>>>> one but I the goal of course is to not have much against the 2.5 branch.
>>>>>
>>>>> @Peter
>>>>> This is what we are working on. The very simple proprietary github
>>>>> tracker (one of the few non open source parts of github so we can't
>>>>> actually send improvement suggestions) is not currently adequate for
>>>>> managing close to 100 people with status changing privileges and does not
>>>>> have adequate complex search and sort capabilities (although the tagging
>>>>> system has real potential) and does not have a seamless way to manage the
>>>>> links between codeless issue reports (which are very common in the CMS) and
>>>>> proposed fixes [e.g. you have to manually get the issue number and type it
>>>>> in your comment--even for the initial reporter later submitting code they
>>>>> have to be very specific in how they do the link to make them connect] or
>>>>> for duplicate report tracking (a joomlacode feature I am probably the only
>>>>> person using). Also in jbs it is extremely important to track manual
>>>>> testing and to also to have excellent reporting capabilities. Even in
>>>>> the comparatively slow low volume platform tracker you see that once it's
>>>>> above 100 open issues it's really kind of a pain and that when people make
>>>>> a report and disappear the reports tend to just fade away rather then have
>>>>> someone else step in and fix. However we hope that is what Joomla can help
>>>>> us with. (Also github itself has been adding useful new APIs.)
>>>>>
>>>>> We also need to solve the issue of attachments that are not pull
>>>>> requests whether sample extensions illustrating problems or screenshots.
>>>>>
>>>>> Some of the issues relate to people needing to get better at using git
>>>>> hub feature such as sending pull requests to each other and pulling
>>>>> branches from people not just from master.
>>>>>
>>>>> JBS has always been about social coding and I'm really anxious to get
>>>>> to the point where we are fully taking advantage of what github offers for
>>>>> that.
>>>>>
>>>>> Elin
>>>>>
>>>>> On Friday, October 5, 2012 7:09:11 AM UTC-4, Kevin wrote:
>>>>>>
>>>>>> "Or drop Joomlacode and svn completely and just use the built in
>>>>>> functionality of github :)"
>>>>>> But could everyone in bugsquad comment inGit Without having to
>>>>>> install and configure software. Also in Git is there one place where the
>>>>>> bugs for each version of Joomla can be posted. From what I've seen of Git
>>>>>> there is no url that an ordinary user can go to.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Friday, 5 October 2012 10:34:58 UTC+1, Peter van Westen wrote:
>>>>>>>
>>>>>>> Or drop Joomlacode and svn completely and just use the built in
>>>>>>> functionality of github :)
>>>>>>>
>>>>>>> On Friday, 5 October 2012 08:41:05 UTC+2, Samuel Moffatt wrote:
>>>>>>>>
>>>>>>>> What I would suggest is filing a bug with the GForge folk to add it
>>>>>>>> as
>>>>>>>> an option to their package.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Sam Moffatt
>>>>>>>> http://pasamio.id.au
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Oct 4, 2012 at 7:17 AM, Mark Dexter <dexter...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> > Unfortunately, we don't have access to the source code for
>>>>>>>> Joomlacode
>>>>>>>> > or the tracker. That is one of the reasons we have looked at
>>>>>>>> trying to
>>>>>>>> > replace it, preferably with a Joomla-based system. Unfortunately,
>>>>>>>> it
>>>>>>>> > takes a lot of time to research this and we all have limited
>>>>>>>> time. So,
>>>>>>>> > as far as I know, there is nothing we can do to accomplish this.
>>>>>>>> If
>>>>>>>> > someone else knows something more about it, please let me know.
>>>>>>>> >
>>>>>>>> > Thanks. Mark
>>>>>>>> >
>>>>>>>> > On Thu, Oct 4, 2012 at 2:35 AM, Peter van Westen
>>>>>>>> > <peterva...@gmail.com> wrote:
>>>>>>>> >> I think it would be useful to color code the table cells under
>>>>>>>> 'Status' in
>>>>>>>> >> the tracker
>>>>>>>> >> (
>>>>>>>> http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103)
>>>>>>>>
>>>>>>>> >> So you can quickly see if a tracker item is closed or pending or
>>>>>>>> open, etc.
>>>>>>>> >>
>>>>>>>> >> I offer to implement this if I can get access to the files/code.
>>>>>>>> >>
>>>>>>>> >> --
>>>>>>>> >> You received this message because you are subscribed to the
>>>>>>>> Google Groups
>>>>>>>> >> "Joomla! bug Squad" group.
>>>>>>>> >> To view this discussion on the web visit
>>>>>>>> >> https://groups.google.com/d/msg/joomlabugsquad/-/zamaReIVPcQJ.
>>>>>>>> >> To post to this group, send email to joomlab...@googlegroups.com.
>>>>>>>>
>>>>>>>> >> To unsubscribe from this group, send email to
>>>>>>>> >> joomlabugsqua...@googlegroups.com.
>>>>>>>> >> For more options, visit this group at
>>>>>>>> >> http://groups.google.com/group/joomlabugsquad?hl=en.
>>>>>>>> >
>>>>>>>> > --
>>>>>>>> > You received this message because you are subscribed to the
>>>>>>>> Google Groups "Joomla! bug Squad" group.
>>>>>>>> > To post to this group, send email to joomlab...@googlegroups.com.
>>>>>>>>
>>>>>>>> > To unsubscribe from this group, send email to
>>>>>>>> joomlabugsqua...@googlegroups.com.
>>>>>>>> > For more options, visit this group at
>>>>>>>> http://groups.google.com/group/joomlabugsquad?hl=en.
>>>>>>>> >
>>>>>>>>
>>>>>>>
------=_Part_167_17668410.1349526075942
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<div style=3D"margin-left: 40px;">"I don't see what commenting and installi=
ng software have to do with each other"<br></div>What is the url for Git th=
at has a list of all the Joomla pull requests so that a non dev can decide =
which bug they can test/comment on ?<br>Where is the url for the list on Gi=
t where non devs can report bugs ?<br><div style=3D"margin-left: 40px;"><br=
></div><div style=3D"margin-left: 40px;">"In github you can also make a pat=
ch+ issue a pull request right on the web"<br></div>Now either I missed tha=
t or it has never been stated before. All the tutorials I have seen l=
inks to have required syncing the computer with Git(in some way or other.)<=
br>Link to a tutorial on how to do pull requests on the web would be good t=
hanks. Because every thing I've looked at requires all sorts of confi=
guration before a patch can be applied. <br><br>For the umpteenth time test=
ing a Git patch is more complex(initially) than testing an SVN patch. =
With svn install one piece of software, point it at the svn trunk put in u=
ser pass ... done. Download the patch right click ... done. But=
with Git download the software configure to sync with Git and a load of ot=
her things ... because the software that is used to test a Git patch will n=
ot work unless you have the whole caboose. <br><br>btw Tortoisesvn wi=
ll download the 2.5 git branch to the computer but not the trunk.<br><br><b=
r><br>On Saturday, 6 October 2012 01:58:22 UTC+1, Elin wrote:<blockquote c=
lass=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px=
#ccc solid;padding-left: 1ex;">For both github and joomlacode forum users =
have to register a new account and learn how to report. <div><br></di=
v><div>I don't see what commenting and installing software have to do with =
each other. If you want to make a comment use the web ui to make a comment.=
That's exactly the same in both. </div><div><br></div><div>Unlike gF=
orge, Git hub does not have a built in form building UI for administr=
ators so it loses in the ability to ask or even require reporters to provid=
e crucial information like cms version, php version. database and bro=
wser. Also github does not have duplicate tracking or a way to upload=
files. It also does not have query building/saving and downloading to csv =
or xls. So advantage gForge for those items.</div><div><br></div><div=
>In github you can also make a patch+ issue a pull request right on the web=
. I've gotten dozens of people to make contributions by saying just go to t=
he file, click edit, make the change and click save. So for beginners with =
simple change proposals github wins hands down. You don't even have to lear=
n to work with a diff file. There is no equivalent of that in gforge+svn. A=
dantage github.</div><div><br></div><div>So for people reporting issues and=
making simple suggested changes in code, things are either equivalent or s=
lightly to the advantage of github.</div><div><br></div><div>For people who=
want to test I really think it depends on what process you use. &nbs=
p;For me, pulling a patch from github or from joomlacode is the same. I app=
ly patches in the same way and test in the same way. I keep one messy=
branch where I apply maybe a dozen jbs patches and then periodically=
, when they are going to interfere with each other, I reset the whole thing=
. That's exactly what I did in svn except it was one checkout. For bo=
th svn and git I installed software to help me manage things. </div><=
div><br>For people who want to write code, I think at this point the =
consensus seems to be that github is easier and more encouraging of collabo=
ration.</div><div><br></div><div>The real issue I care personally about in =
a self-interested way is which system makes it easiest to manage a tracker =
with typically 400-600 open issues and, in fact, a number of separate thing=
s i.e. a 2.5 tracker, a trunk tracker, a feature tracker, and a security tr=
acker, and a number of trackers with historical function, plus a large numb=
er of people working in different places. Which lets me keep the most=
open issues in my working memory and which makes it easiest to find an old=
issue when I think "I know I have seen that issue before"? Also what=
system is JM going to complain about least :P. For the latter I'd st=
rongly like an open source solution since the main problem with both option=
s we have been discussing is that the only work we can do to make it work t=
he way we want is to use apis. From what I have seen the github apis are mu=
ch easier to work with.</div><div><br></div><div>Elin</div><div><br></div><=
div><br><br>On Friday, October 5, 2012 7:06:05 PM UTC-4, Kevin wrote:<block=
quote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left=
:1px #ccc solid;padding-left:1ex"><blockquote style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=3D"gmai=
l_quote"><div style=3D"margin-left:40px">"<i>While people sending code can =
easily indicate which branch the code is=20
for, people making issue reports don't have an easy way to mark that=20
(because even if jbs can apply tags new reporters won't have access to=20
the tagging"</i><br></div></blockquote>That is exactly what I meant when I =
said<br><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
rgb(204,204,204);padding-left:1ex" class=3D"gmail_quote"><div style=3D"mar=
gin-left:40px">"<i>But could everyone in bugsquad comment inGit Without hav=
ing to install and configure software</i>"<br></div></blockquote><br>Yes th=
ere are pitfalls with Joomlacode tracker but to "<i>Or drop Joomlacode and =
svn completely and just use the built in functionality of github :)</i>"&nb=
sp; ... might have more pitfalls. After all if a user in the forums r=
eports a bug then ... with the current system in Joomlacode ... it is a sim=
ple mater to report the bug after testing. And I have even managed to=
test a few simple patches as well.<br><br>I enjoy helping out in bugsquad =
but feel that it could easy to fall behind with too many changes. And=
wonder how many other non-developers could get left behind as well? =
Not trying to be obstructive of improvement ... just putting a point of vie=
w that <i>"Or drop Joomlacode and svn completely and just use the built in =
functionality of github :)"</i> may not be a change for the best. And=
explaining my thought process for why not.<br><br><br>On Friday, 5 October=
2012 23:43:42 UTC+1, Elin wrote:<blockquote class=3D"gmail_quote" style=
=3D"margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div><a href=3D"https://github.com/joomla/joomla-cms/issues" target=3D"_bl=
ank">https://github.com/joomla/<wbr>joomla-cms/issues</a><br></div>Just com=
ment and say what version and if you are making a pull request specify the =
correct target branch (master for J3, 2.5 for 2.5). But that is a gre=
at example of why the github tracker is not really workable without help. W=
hile people sending code can easily indicate which branch the code is for, =
people making issue reports don't have an easy way to mark that (because ev=
en if jbs can apply tags new reporters won't have access to the tagging plu=
s they won't realize that it's needed just like on any other web UI people =
will not read instructions that you can be sure of). <div><br></div><d=
iv>I don't understand the "you:" in your comment .. the whole point i=
s we want to keep what we have which is close to 100 people able to c=
hange statuses. I also have no idea what 'devs' you are talking about=
but I'm pretty sure Mark and JM want more help not less. What we need is a=
solution that maps well to the current processes that we have and are sati=
sfied with and that as much as possible fixes the ones that we aren't. &nbs=
p;The way the JBS works is pretty unusual and that has made finding a produ=
ct that maps well to it difficult. We don't want JBS to have to fit a track=
er we want a tracker to have to fit JBS.</div><div><br></div><div><br></div=
><div>Currently we have about 609 issues with some kind of open status on t=
he main tracker on joomlacode. </div><div><a href=3D"https://github.co=
m/popular/starred" target=3D"_blank">https://github.com/popular/<wbr>starre=
d</a> on that list I think Rails is the only one that comes close to =
that although it's confusing where their numbers are coming from. <br>=
</div><div><br></div><div>Elin</div><div><br>On Friday, October 5, 2012 11:=
40:12 AM UTC-4, Kevin wrote:<blockquote class=3D"gmail_quote" style=3D"marg=
in:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">@Elin<b=
r><br>What is the url on Git for the comments on J3 and where is the url fo=
r the comments on 2,5 ? All I can see is lots of individual discussio=
ns on each individual pull request page. At least with Joomla code th=
ere is only 1 url for each version of Joomla.<br><br><div style=3D"margin-l=
eft:40px">" <i>is not currently adequate for managing close to 100 people w=
ith status changing privileges</i>"<br></div>That can get complicated but i=
f you want to limit it to just the Dev's being able to do that ... then fin=
e no problem with that. More work for the Devs and less work for the =
Testers/ticket handlers.<br><br><div style=3D"margin-left:40px">"<i>Even in=
the comparatively slow low volume platform tracker you see that=
=20
once it's above 100 open issues it's really kind of a pain and that when
people make a report and disappear the reports tend to just fade away=20
rather then have someone else step in and fix</i>"<br></div>Yes, but is tha=
t not true about any list with 100+ entries, no matter where the list is ?<=
br><br><br><br>On Friday, 5 October 2012 12:51:24 UTC+1, Elin wrote:<block=
quote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div>@Kevin I'm not sure what you mean, a=
ny one can comment on any issue in github, you just need to login and you c=
an put both attached comments and inline comments. I do think that there wi=
ll be an issue when people need to make pull requests against both the 2.5 =
branch and against master or just one but I the goal of course is to not ha=
ve much against the 2.5 branch.</div><div><br></div><div>@Peter</div>This i=
s what we are working on. The very simple proprietary github tracker (one o=
f the few non open source parts of github so we can't actually send improve=
ment suggestions) is not currently adequate for managing close to 100 peopl=
e with status changing privileges and does not have adequate complex search=
and sort capabilities (although the tagging system has real potential) and=
does not have a seamless way to manage the links between codeless issue re=
ports (which are very common in the CMS) and proposed fixes [e.g. you have =
to manually get the issue number and type it in your comment--even for the =
initial reporter later submitting code they have to be very specific in how=
they do the link to make them connect] or for duplicate report tracking (a=
joomlacode feature I am probably the only person using). Also in jbs=
it is extremely important to track manual testing and to also to hav=
e excellent reporting capabilities. Even in the comparatively slo=
w low volume platform tracker you see that once it's above 100 open issues =
it's really kind of a pain and that when people make a report and disappear=
the reports tend to just fade away rather then have someone else step in a=
nd fix. However we hope that is what Joomla can help us with. (A=
lso github itself has been adding useful new APIs.)<div><br></div><div>We a=
lso need to solve the issue of attachments that are not pull requests wheth=
er sample extensions illustrating problems or screenshots.</div><div><br></=
div><div>Some of the issues relate to people needing to get better at using=
git hub feature such as sending pull requests to each other and pulling br=
anches from people not just from master. <br><div><div><br></div><div>=
JBS has always been about social coding and I'm really anxious to get to th=
e point where we are fully taking advantage of what github offers for that.=
</div><div><br></div><div>Elin<br><br>On Friday, October 5, 2012 7:09:11 AM=
UTC-4, Kevin wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0;mar=
gin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"m=
argin-left:40px">"Or drop Joomlacode and svn completely and just use the bu=
ilt in functionality of github :)"<br></div>But could everyone in bugsquad =
comment inGit Without having to install and configure software. Also =
in Git is there one place where the bugs for each version of Joomla can be =
posted. From what I've seen of Git there is no url that an ordinary u=
ser can go to.<br><br><br><br>On Friday, 5 October 2012 10:34:58 UTC+1, Pet=
er van Westen wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0;ma=
rgin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">Or drop Joomla=
code and svn completely and just use the built in functionality of github :=
)<br><br>On Friday, 5 October 2012 08:41:05 UTC+2, Samuel Moffatt wrote:<b=
lockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-=
left:1px #ccc solid;padding-left:1ex">What I would suggest is filing a bug =
with the GForge folk to add it as
<br>an option to their package.
<br>
<br>Cheers,
<br>
<br>Sam Moffatt
<br><a href=3D"http://pasamio.id.au" target=3D"_blank">http://pasamio.id.au=
</a>
<br>
<br>
<br>On Thu, Oct 4, 2012 at 7:17 AM, Mark Dexter <<a>dexter...@gmail.com<=
/a>> wrote:
<br>> Unfortunately, we don't have access to the source code for Joomlac=
ode
<br>> or the tracker. That is one of the reasons we have looked at tryin=
g to
<br>> replace it, preferably with a Joomla-based system. Unfortunately, =
it
<br>> takes a lot of time to research this and we all have limited time.=
So,
<br>> as far as I know, there is nothing we can do to accomplish this. I=
f
<br>> someone else knows something more about it, please let me know.
<br>>
<br>> Thanks. Mark
<br>>
<br>> On Thu, Oct 4, 2012 at 2:35 AM, Peter van Westen
<br>> <<a>peterva...@gmail.com</a>> wrote:
<br>>> I think it would be useful to color code the table cells under=
'Status' in
<br>>> the tracker
<br>>> (<a href=3D"http://joomlacode.org/gf/project/joomla/tracker/?a=
ction=3DTrackerItemBrowse&tracker_id=3D8103" target=3D"_blank">http://j=
oomlacode.org/gf/<wbr>project/joomla/tracker/?<wbr>action=3DTrackerItemBrow=
se&<wbr>tracker_id=3D8103</a>)
<br>>> So you can quickly see if a tracker item is closed or pending =
or open, etc.
<br>>>
<br>>> I offer to implement this if I can get access to the files/cod=
e.
<br>>>
<br>>> --
<br>>> You received this message because you are subscribed to the Go=
ogle Groups
<br>>> "Joomla! bug Squad" group.
<br>>> To view this discussion on the web visit
<br>>> <a href=3D"https://groups.google.com/d/msg/joomlabugsquad/-/za=
maReIVPcQJ" target=3D"_blank">https://groups.google.com/d/<wbr>msg/joomlabu=
gsquad/-/<wbr>zamaReIVPcQJ</a>.
<br>>> To post to this group, send email to <a>joomlab...@googlegroup=
s.com</a>.
<br>>> To unsubscribe from this group, send email to
<br>>> <a>joomlabugsqua...@googlegroups.<wbr>com</a>.
<br>>> For more options, visit this group at
<br>>> <a href=3D"http://groups.google.com/group/joomlabugsquad?hl=3D=
en" target=3D"_blank">http://groups.google.com/<wbr>group/joomlabugsquad?hl=
=3Den</a>.
<br>>
<br>> --
<br>> You received this message because you are subscribed to the Google=
Groups "Joomla! bug Squad" group.
<br>> To post to this group, send email to <a>joomlab...@googlegroups.co=
m</a>.
<br>> To unsubscribe from this group, send email to <a>joomlabugsqua...@=
googlegroups.<wbr>com</a>.
<br>> For more options, visit this group at <a href=3D"http://groups.goo=
gle.com/group/joomlabugsquad?hl=3Den" target=3D"_blank">http://groups.googl=
e.com/<wbr>group/joomlabugsquad?hl=3Den</a>.
<br>>
<br></blockquote></blockquote></blockquote></div></div></div></blockquote><=
/blockquote></div></blockquote></blockquote></div></blockquote>
------=_Part_167_17668410.1349526075942--
------=_Part_166_17793465.1349526075942--
Message from discussion Colors on status in Joomlacode bug tracker
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2013 Google |