No subject
Sat Oct 16 04:25:36 CEST 2010
This mailing list is an informational list to which commit descriptions for=
patches pushed to the public Koha Git repository (currently git://git.koha=
-community.org/koha.git) are posted.
This list should not be used to discuss individual patches, as not all cont=
ributors will be subscribed to koha-commits. Instead, please use koha-devel=
, koha-patches, or bugs.koha.org for that purpose.
Is this no longer the case?
-----Oorspronkelijk bericht-----
Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces=
@lists.koha-community.org] Namens MJ Ray
Verzonden: maandag 15 november 2010 11:10
Aan: Galen Charlton
CC: koha-devel at lists.koha-community.org; koha-patches at lists.koha-community.=
org
Onderwerp: [Koha-devel] Discussion of development topics, was: Bug 5401: WY=
SWYG for Koha News
Galen Charlton wrote:
> There is a long standing practice of discussion of individual patches
> on koha-commits, however, so while koha-devel is certainly a valid
> choice for discussing this issue, I do want to point out and remind
> people that some relevant discussion does take place on the
> koha-commits list.
I don't like that practice because:-
1. the list description "Patches submitted to Koha" gives no
indication it occurs and it's different from other projects' -commit
mailing lists;
2. developers have to subscribe to receive all patches even if they're
only interested in their fields of activity and the occasional
discussions, contributing to information overload;
3. I think the patches are carried in only one of the web forum
versions of our discussions http://koha-community.org/support/forums/
4. usually the patches relate to a bug and email discussion isn't
automatically attached to the bug report - I have started work to
address this, but it's still going to have some delay between
the discussion and posting to the bug report, which may mean the
discussion is irrelevant by the time the bug is told;
5. most importantly, many topics are wider than a single patch,
such as this one about what rich editor to adopt.
Can we overcome these problems, or state clearly that
wider-than-one-patch discussions should be on -devel?
Thanks,
--
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire for Koha work http://www.software.coop/products/koha
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--_000_809BE39CD64BFD4EB9036172EBCCFA311A2195SMAIL1Brijksmuseu_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Tekst zonder opmaak Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Verdana","sans-serif";}
span.TekstzonderopmaakChar
{mso-style-name:"Tekst zonder opmaak Char";
mso-style-priority:99;
mso-style-link:"Tekst zonder opmaak";
font-family:"Verdana","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">From the koha-commits mailing list:<o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">This mailing list is an informational list to whi=
ch commit descriptions for patches pushed to the public Koha Git repository=
(currently git://git.koha-community.org/koha.git) are posted.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><b>This list should not be used to discuss indivi=
dual patches</b>, as not all contributors will be subscribed to koha-commit=
s. Instead, please use koha-devel, koha-patches, or bugs.koha.org for that =
purpose.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Is this no longer the case? <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"NL">-----Oorspronkelijk bericht----=
-<br>
Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces=
@lists.koha-community.org] Namens MJ Ray<br>
Verzonden: maandag 15 november 2010 11:10<br>
Aan: Galen Charlton<br>
CC: koha-devel at lists.koha-community.org; koha-patches at lists.koha-community.=
org<br>
Onderwerp: [Koha-devel] Discussion of development topics, was: Bug 5401: WY=
SWYG for Koha News</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Galen Charlton wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText">> There is a long standing practice of discuss=
ion of individual patches<o:p></o:p></p>
<p class=3D"MsoPlainText">> on koha-commits, however, so while koha-deve=
l is certainly a valid<o:p></o:p></p>
<p class=3D"MsoPlainText">> choice for discussing this issue, I do want =
to point out and remind<o:p></o:p></p>
<p class=3D"MsoPlainText">> people that some relevant discussion does ta=
ke place on the<o:p></o:p></p>
<p class=3D"MsoPlainText">> koha-commits list.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">I don't like that practice because:-<o:p></o:p></=
p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">1. the list description "Patches submitted t=
o Koha" gives no<o:p></o:p></p>
<p class=3D"MsoPlainText">indication it occurs and it's different from othe=
r projects' -commit<o:p></o:p></p>
<p class=3D"MsoPlainText">mailing lists;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">2. developers have to subscribe to receive all pa=
tches even if they're<o:p></o:p></p>
<p class=3D"MsoPlainText">only interested in their fields of activity and t=
he occasional<o:p></o:p></p>
<p class=3D"MsoPlainText">discussions, contributing to information overload=
;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">3. I think the patches are carried in only one of=
the web forum<o:p></o:p></p>
<p class=3D"MsoPlainText">versions of our discussions http://koha-community=
.org/support/forums/<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">4. usually the patches relate to a bug and email =
discussion isn't<o:p></o:p></p>
<p class=3D"MsoPlainText">automatically attached to the bug report - I have=
started work to<o:p></o:p></p>
<p class=3D"MsoPlainText">address this, but it's still going to have some d=
elay between<o:p></o:p></p>
<p class=3D"MsoPlainText">the discussion and posting to the bug report, whi=
ch may mean the<o:p></o:p></p>
<p class=3D"MsoPlainText">discussion is irrelevant by the time the bug is t=
old;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">5. most importantly, many topics are wider than a=
single patch,<o:p></o:p></p>
<p class=3D"MsoPlainText">such as this one about what rich editor to adopt.=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Can we overcome these problems, or state clearly =
that<o:p></o:p></p>
<p class=3D"MsoPlainText">wider-than-one-patch discussions should be on -de=
vel?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">-- <o:p></o:p></p>
<p class=3D"MsoPlainText">MJ Ray (slef), member of www.software.coop, a for=
-more-than-profit co-op.<o:p></o:p></p>
<p class=3D"MsoPlainText">Past Koha Release Manager (2.0), LMS programmer, =
statistician, webmaster.<o:p></o:p></p>
<p class=3D"MsoPlainText">In My Opinion Only: see http://mjr.towers.org.uk/=
email.html<o:p></o:p></p>
<p class=3D"MsoPlainText">Available for hire for Koha work http://www.softw=
are.coop/products/koha<o:p></o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">Koha-devel mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">Koha-devel at lists.koha-community.org<o:p></o:p></p=
>
<p class=3D"MsoPlainText">http://lists.koha-community.org/cgi-bin/mailman/l=
istinfo/koha-devel<o:p></o:p></p>
<p class=3D"MsoPlainText">website : http://www.koha-community.org/<o:p></o:=
p></p>
<p class=3D"MsoPlainText">git : http://git.koha-community.org/<o:p></o:p></=
p>
<p class=3D"MsoPlainText">bugs : http://bugs.koha-community.org/<o:p></o:p>=
</p>
</div>
</body>
</html>
--_000_809BE39CD64BFD4EB9036172EBCCFA311A2195SMAIL1Brijksmuseu_--
More information about the Koha-devel
mailing list