Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@do...> - 2012-08-23 17:06:42
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Upgrade to Lucene.Net 3.0.3</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Query.FullText (dotNetRDF.Query.FullText.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Milestone changed from "none" to "Unscheduled"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=275" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=275</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2012-08-23 16:59:42
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Upgrade to Lucene.Net 3.0.3</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Query.FullText (dotNetRDF.Query.FullText.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>none</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Lucene</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Refactor</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Once Lucene.Net 3.0.3 is released we should upgrade to this, it will require some refactoring as the Lucene.Net project has now moved to .Net`fying the library where the 2.9.2 and 2.9.4 builds were very much straight ports from Java.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=275" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=275</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2012-08-23 16:55:29
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>PersistentGraphCollection can hit a StackOverflowException when retrieving a Graph</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "none" to "Fixed"
</li>
<li>Progress changed from "0.00 %" to "10,000.00 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=274" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=274</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2012-08-23 16:55:25
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>PersistentGraphCollection can hit a StackOverflowException when retrieving a Graph</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2012-08-23 05:54 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Fixed in revision 2376</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=274" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=274</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2012-08-23 16:52:37
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>PersistentGraphCollection can hit a StackOverflowException when retrieving a Graph</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>0.7.2 Beta</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Critical</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
It turns out that the refactor of GraphCollection to use MultiDictionary had a slight flaw that means classes that override Contains() such as PersistentGraphCollection can hit a StackOverflowException in some circumstances.</p>
<p>
</p>
<p>
The cause is that Add() is calling the class level Contains() when it should only be calling ContainsKey() on the MultiDictionary itself.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=274" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=274</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Tomasz P. <tom...@gm...> - 2012-08-23 10:31:17
|
It is working now. Thanks Rob. Tom On Wed, Aug 22, 2012 at 5:53 PM, Rob Vesse <rv...@vd...> wrote: > Sorry they changed some of the configuration settings as part of the new > version (I jumped about 4 releases with the upgrade) and it seems they now > default to public registration being turned off > > It should now be turned back on again > > Rob > > On 8/22/12 12:47 AM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Hi >> >>As the tracker finally works I wanted to see if I can submit a feature >>proposal but I can't. IMO the tracker could be made open or at least >>offer registration. What do you think? Or am I missing something? >> >>Regards, >>Tomasz >> >>-------------------------------------------------------------------------- >>---- >>Live Security Virtual Conference >>Exclusive live event will cover all the ways today's security and >>threat landscape has changed and how IT managers can respond. Discussions >>will include endpoint security, mobile security and the latest in malware >>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-08-22 19:52:46
|
Hey Graham If you would like to be added as a committer for dotNetRDF can you let me know your SourceForge username Thanks, Rob |
|
From: Khalil A. <ka...@ne...> - 2012-08-22 16:41:18
|
Hi Rob, Making use of ThreadLocal<T> on .NET 4.0 definitely is a good change. However, today the WinRT port has hit something of a dead-end because of two things I didn't realize about WinRT a) All exported (public) classes must be sealed b) Indexer properties are not supported There is also another show-stopper issue to do with the overriding of virtual methods where the class you are deriving from itself overrides the same method on its base class - I haven't found the reasoning behind this or a way to work around it, but given the other two major issues I don't think a WinRT port would be as simple to do as the Silverlight / WindowsPhone ones. So for now WinRT is going on my back-burner :) Cheers Kal On Wed, Aug 22, 2012 at 5:12 PM, Rob Vesse <rv...@vd...>wrote: > Yes the code was written for .Net 3.5 so before ThreadLocal<T> came along, > also ThreadLocal<T> is not supported on Silverlight/Windows Phone 7 > > I have refactored the code in Trunk to use ThreadLocal<T> when running on > .Net 4.0 non-Silverlight platforms > > Hope this helps > > Rob > > From: Kal Ahmed <ka...@ne...> > Reply-To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Date: Tuesday, August 21, 2012 11:33 PM > To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Subject: [dotNetRDF-Develop] ThreadIsolatedReference/ThreadIsolatedValue > classes > > Hi Rob, > > I'm having a fun time trying to hack a WinRT build of dotNetRDF. Amongst > other bits of WTF (like all the IO being different, and streams no longer > having a Close() method), the System.Threading.Thread class is not provided > under WinRT which means I can't compile the ThreadIsolatedReference. > However, from a cursory reading it seems like > System.Threading.ThreadLocal<T> does more or less what you need (though it > probably needs to be wrapped to provide the initialization functionality of > ThreadIsolatedReference). > > Is this just a backwards compatability thing for pre 4.0 versions of .NET > or is there another reason why you stayed away from ThreadLocal<T> ? > > Cheers > > Kal > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > t: +44 1865 811131 > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the > ways today's security and threat landscape has changed and how IT managers > can respond. Discussions will include endpoint security, mobile security > and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com t: +44 1865 811131 |
|
From: Rob V. <rv...@vd...> - 2012-08-22 16:13:43
|
Yes the code was written for .Net 3.5 so before ThreadLocal<T> came along, also ThreadLocal<T> is not supported on Silverlight/Windows Phone 7 I have refactored the code in Trunk to use ThreadLocal<T> when running on .Net 4.0 non-Silverlight platforms Hope this helps Rob From: Kal Ahmed <ka...@ne...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Tuesday, August 21, 2012 11:33 PM To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: [dotNetRDF-Develop] ThreadIsolatedReference/ThreadIsolatedValue classes > Hi Rob, > > I'm having a fun time trying to hack a WinRT build of dotNetRDF. Amongst other > bits of WTF (like all the IO being different, and streams no longer having a > Close() method), the System.Threading.Thread class is not provided under WinRT > which means I can't compile the ThreadIsolatedReference. However, from a > cursory reading it seems like System.Threading.ThreadLocal<T> does more or > less what you need (though it probably needs to be wrapped to provide the > initialization functionality of ThreadIsolatedReference). > > Is this just a backwards compatability thing for pre 4.0 versions of .NET or > is there another reason why you stayed away from ThreadLocal<T> ? > > Cheers > > Kal > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> > t: +44 1865 811131 <tel:%2B44%201865%20811131> > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the ways > today's security and threat landscape has changed and how IT managers can > respond. Discussions will include endpoint security, mobile security and the > latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_____________________ > __________________________ dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@vd...> - 2012-08-22 15:54:22
|
Sorry they changed some of the configuration settings as part of the new version (I jumped about 4 releases with the upgrade) and it seems they now default to public registration being turned off It should now be turned back on again Rob On 8/22/12 12:47 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi > >As the tracker finally works I wanted to see if I can submit a feature >proposal but I can't. IMO the tracker could be made open or at least >offer registration. What do you think? Or am I missing something? > >Regards, >Tomasz > >-------------------------------------------------------------------------- >---- >Live Security Virtual Conference >Exclusive live event will cover all the ways today's security and >threat landscape has changed and how IT managers can respond. Discussions >will include endpoint security, mobile security and the latest in malware >threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2012-08-22 07:48:31
|
Hi As the tracker finally works I wanted to see if I can submit a feature proposal but I can't. IMO the tracker could be made open or at least offer registration. What do you think? Or am I missing something? Regards, Tomasz |
|
From: Khalil A. <ka...@ne...> - 2012-08-22 06:54:27
|
Hi Rob, OK, so the separate question is about the extent of regression testing for commits. The current unit testing framework for the project allows for the third party stores to be optionally present. My question is that do you have a preference for what level of regression testing is done on changes to core ? Currently I don't have any of the third-party stores installed on any of my dev machines / VMs, so although I can run quite a significant proportion of the unit tests, there are quite a number that get skipped. Is that a big problem ? Should I install at least one (or more) of these stores and ensure that the unit tests for that store run correctly before committing ? Ideally I would like to avoid having to install them all...but am I just being lazy ? Cheers KAl -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com t: +44 1865 811131 |
|
From: Khalil A. <ka...@ne...> - 2012-08-22 06:39:21
|
Hi Rob, I'm having a fun time trying to hack a WinRT build of dotNetRDF. Amongst other bits of WTF (like all the IO being different, and streams no longer having a Close() method), the System.Threading.Thread class is not provided under WinRT which means I can't compile the ThreadIsolatedReference. However, from a cursory reading it seems like System.Threading.ThreadLocal<T> does more or less what you need (though it probably needs to be wrapped to provide the initialization functionality of ThreadIsolatedReference). Is this just a backwards compatability thing for pre 4.0 versions of .NET or is there another reason why you stayed away from ThreadLocal<T> ? Cheers Kal -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com t: +44 1865 811131 |
|
From: Khalil A. <ka...@ne...> - 2012-08-22 06:25:57
|
Hi Rob, Sounds good to me. I have a specific question about regression testing but I'll start it on a separate thread. Cheers Kal On Tue, Aug 21, 2012 at 6:40 PM, Rob Vesse <rv...@do...> wrote: > Kal > > Comments inline > > From: Kal Ahmed <ka...@ne...> > Reply-To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Date: Tuesday, August 21, 2012 12:59 AM > To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Subject: Re: [dotNetRDF-Develop] Open/Proposed Committer Invites > > Hi Rob, > > Thanks for inviting us to join you on the project! I look forward to > hopefully making some useful contributions :) > > One thing I would be keen for us to discuss and agree is what procedures > we want to adopt as a group for dealing both with bugs and with feature > requests / extensions of the project. Its probably not possible to cover > every potential possibility but at least having some idea about whether it > is OK to go in a fix bugs from the list; what you should do if you find a > bug and have a patch (i.e. report it first or just patch it); and what to > do about ideas for extensions / features etc. > > In general I think it would work best if there is communication on this > list, even if it is just along the lines of "guys, I found this bug, did X > to fix it and I'm ready to commit" to give others a chance to explain why > it is a feature and not a bug :) For bigger things, I think a longer > discussion would probably be useful to make sure we are on the same page. > > > Personally I tend to prefer the Apache style of CTR (commit then review) > rather than the RTC (review than commit) style depending on what you are > working on, we all have access to the repositories and the logs so we all > can review other commits. On this point I would say please make sure you > write descriptive commit messages, especially if your commit touches a lot > of files. I always like being able to glance at the log and not have to > dig into the actual diffs to know what changed. Related to this if you > change/fix something try and remember to add it to the Change Log, there's > a core library specific one under Libraries/core and a toolkit one under > Utilities. > > I would agree that for new features and extensions it is sensible to have > some degree of discussion on the list so we make sure everyone is in > agreement on whether to add a feature/extension and how to go about it. > > However for bug fixes I would generally prefer that developers use their > discretion. Make sure to write some unit test(s) that reproduce the bug, > try to make a fix for the bug and check that your new tests pass AND that > you haven't caused any existing tests to fail. If existing tests fail try > to figure out why, in some cases it may be that the existing tests were > silently assuming the old buggy behavior in which case fix those as well. > If it isn't clear why the fix causes a regression elsewhere or you just > aren't sure what the implications of making a change are then it would be > sensible to start a discussion on the list before you commit. But if you > can fix the bug and all the tests still pass then please go ahead and > commit it. If we find out the fix causes other issues at a later point we > can always revert or rework that commit as appropriate. > > I will be the first to admit that RDF/SPARQL etc can be somewhat arcane at > times and I know me and Kal have gone back and forth on some thorny bugs in > the past where one bug was hiding another bug and so it wasn't clear > whether the behavior he was seeing was actually a bug or not. If in doubt > ask, if you can fix it without introducing regressions fix it. > > Rob > > > What do y'all think ? > > Cheers > > Kal > > On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...>wrote: > >> As you've all probably noticed I've been trying to grow the committers >> list lately because I don't want to have to do all the work myself nor do I >> need/want to review every minor patch. If someone has proved their ability >> by contributing over time I want to give them the opportunity to become >> more involved with the project if they desire. >> >> With this in mind we currently have the following committer invites open >> to Tomasz Pluskiewicz. >> >> I would also like to take the opportunity to invite Graham Moore (Kal's >> colleague at NetworkedPlanet) to become a committer if he too wishes, I >> should have done this when I invited Kal but it slipped my mind at the time. >> >> I have one/two other intermittent committers who I may approach privately >> off list first to see if they are still working actively with the project >> and if they are interested in joining as committers. If anyone else has >> potential committers in mind who they know have experience with the API and >> may like to get more involved suggestions are welcome >> >> Thanks, >> >> Rob >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > t: +44 1865 811131 > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the > ways today's security and threat landscape has changed and how IT managers > can respond. Discussions will include endpoint security, mobile security > and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com t: +44 1865 811131 |
|
From: Tomasz P. <tom...@gm...> - 2012-08-21 21:29:00
|
Hi Rob and Kal What you describe below is where DVCS shine. We could achieve exactly the CTR style of workflow easily. A safe and flexible approach is to have the main repository readonly for anyone but a designated maintainer, who would merge other user's work. This would be Rob in our case. With Linux for example each developer creates his own remote repository, which he then pulls locally to work on the code. Let me describe it in steps: 1. Maintainer creates the repository with initial structure available remotely. Let's call it master.remote 2. Developers A and B clone those repositories and get devA.remote and devB.remote respectively 3. Developers A and B then pull from their remote repositories to their computers to get the code and make some changes 4. When they are ready they push the changes back to devA.remote and devB.remote 5. Now the maintainer pulls from devA.remote and devB.remote to his local repository master.local, reviews what has changed and if it is good, merges and pulls to master.remote for others to get Now there are a some important facts. First, each developer can create multiple remote and local clones to easily work on unrelate changes without worrying that somerhing would break. They can do frequent commits and easily discard what is not needed anymore and should not see the light of day :). Second, because anyone can create their own clone of the repository and then ask the maintainer to pull their changes there is no more need for any ACL and granting access to commit. Someone new to the project can invent a feature (maybe discuss it on this list?), clone, implement that feature and share their code with ease. All with much less risk of interrupting other's work. Actually a third party could even clone to create their own private fork. Add their secret features and always stay up-to-date because they can commit in their own clone and pull what changes in the official repository. Tell me if it's clear what I've written here... Regards, Tom On Tue, Aug 21, 2012 at 7:40 PM, Rob Vesse <rv...@do...> wrote: > Kal > > Comments inline > > From: Kal Ahmed <ka...@ne...> > Reply-To: dotNetRDF Developer Discussion and Feature Request > <dot...@li...> > Date: Tuesday, August 21, 2012 12:59 AM > To: dotNetRDF Developer Discussion and Feature Request > <dot...@li...> > Subject: Re: [dotNetRDF-Develop] Open/Proposed Committer Invites > > Hi Rob, > > Thanks for inviting us to join you on the project! I look forward to > hopefully making some useful contributions :) > > One thing I would be keen for us to discuss and agree is what procedures we > want to adopt as a group for dealing both with bugs and with feature > requests / extensions of the project. Its probably not possible to cover > every potential possibility but at least having some idea about whether it > is OK to go in a fix bugs from the list; what you should do if you find a > bug and have a patch (i.e. report it first or just patch it); and what to do > about ideas for extensions / features etc. > > In general I think it would work best if there is communication on this > list, even if it is just along the lines of "guys, I found this bug, did X > to fix it and I'm ready to commit" to give others a chance to explain why it > is a feature and not a bug :) For bigger things, I think a longer discussion > would probably be useful to make sure we are on the same page. > > > Personally I tend to prefer the Apache style of CTR (commit then review) > rather than the RTC (review than commit) style depending on what you are > working on, we all have access to the repositories and the logs so we all > can review other commits. On this point I would say please make sure you > write descriptive commit messages, especially if your commit touches a lot > of files. I always like being able to glance at the log and not have to dig > into the actual diffs to know what changed. Related to this if you > change/fix something try and remember to add it to the Change Log, there's a > core library specific one under Libraries/core and a toolkit one under > Utilities. > > I would agree that for new features and extensions it is sensible to have > some degree of discussion on the list so we make sure everyone is in > agreement on whether to add a feature/extension and how to go about it. > > However for bug fixes I would generally prefer that developers use their > discretion. Make sure to write some unit test(s) that reproduce the bug, > try to make a fix for the bug and check that your new tests pass AND that > you haven't caused any existing tests to fail. If existing tests fail try > to figure out why, in some cases it may be that the existing tests were > silently assuming the old buggy behavior in which case fix those as well. If > it isn't clear why the fix causes a regression elsewhere or you just aren't > sure what the implications of making a change are then it would be sensible > to start a discussion on the list before you commit. But if you can fix the > bug and all the tests still pass then please go ahead and commit it. If we > find out the fix causes other issues at a later point we can always revert > or rework that commit as appropriate. > > I will be the first to admit that RDF/SPARQL etc can be somewhat arcane at > times and I know me and Kal have gone back and forth on some thorny bugs in > the past where one bug was hiding another bug and so it wasn't clear whether > the behavior he was seeing was actually a bug or not. If in doubt ask, if > you can fix it without introducing regressions fix it. > > Rob > > > What do y'all think ? > > Cheers > > Kal > > On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...> > wrote: >> >> As you've all probably noticed I've been trying to grow the committers >> list lately because I don't want to have to do all the work myself nor do I >> need/want to review every minor patch. If someone has proved their ability >> by contributing over time I want to give them the opportunity to become more >> involved with the project if they desire. >> >> With this in mind we currently have the following committer invites open >> to Tomasz Pluskiewicz. >> >> I would also like to take the opportunity to invite Graham Moore (Kal's >> colleague at NetworkedPlanet) to become a committer if he too wishes, I >> should have done this when I invited Kal but it slipped my mind at the time. >> >> I have one/two other intermittent committers who I may approach privately >> off list first to see if they are still working actively with the project >> and if they are interested in joining as committers. If anyone else has >> potential committers in mind who they know have experience with the API and >> may like to get more involved suggestions are welcome >> >> Thanks, >> >> Rob >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > t: +44 1865 811131 > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the > ways today's security and threat landscape has changed and how IT managers > can respond. Discussions will include endpoint security, mobile security and > the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > dotNetRDF-develop mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Tomasz P. <tom...@gm...> - 2012-08-21 21:01:26
|
Hi Rob Comments inline Tome On Tue, Aug 21, 2012 at 7:29 PM, Rob Vesse <rv...@do...> wrote: > Hey Tom > > Comments inline > > On 8/21/12 3:19 AM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Hi >> >>Thanks Rob for inviting me. I hope I will have an opportunity to >>contribute soon enough. >> >>Now, I have some comments for Khal inline below. >> >>Regards, >>Tom >> >>PS >>Oh and you could start addressing me Tom. Tomasz seems awfully formal >>to me anyway. >> >>On Tue, Aug 21, 2012 at 9:59 AM, Khalil Ahmed <ka...@ne...> >>wrote: >>> Hi Rob, >>> >>> Thanks for inviting us to join you on the project! I look forward to >>> hopefully making some useful contributions :) >>> >>> One thing I would be keen for us to discuss and agree is what >>>procedures we >>> want to adopt as a group for dealing both with bugs and with feature >>> requests / extensions of the project. Its probably not possible to cover >>> every potential possibility but at least having some idea about whether >>>it >>> is OK to go in a fix bugs from the list; what you should do if you find >>>a >>> bug and have a patch (i.e. report it first or just patch it); and what >>>to do >>> about ideas for extensions / features etc. >>> >> >>First I still cannot access the tracker (Chrome says >>net::ERR_CONNECTION_RESET). This will be a problem. > > A quick Google search turned up > http://support.google.com/chrome/bin/answer.py?hl=en&answer=117805 which > is Chrome's support article about this error but not sure if it will be of > any help > >> >>Other than that I agree that this list is the current communication >>platform and for now it is the best place to discuss our work. I have >>also been thinking about http://www.uservoice.com/, which could be >>open for people to suggest changes and vote on what other's have >>suggested. This way we could track the actual demand for features. A >>free plan should suffice for the time beeing. >> >>> >>> In general I think it would work best if there is communication on this >>> list, even if it is just along the lines of "guys, I found this bug, >>>did X >>> to fix it and I'm ready to commit" to give others a chance to explain >>>why it >>> is a feature and not a bug :) For bigger things, I think a longer >>>discussion >>> would probably be useful to make sure we are on the same page. >>> >> >>As far as patching is concerned I think you will enjoy Mercurial. Not >>sure how well SF integrates with it, but I think it treats it just as >>SVN, which is a shame. With Bitbucket or Github there is an option to >>fork, which creates a developer's personal copy of the repository >>where he commits changes and the sends a pull request with information >>what changed and which commits should get integrated with the main >>branch. > > I have turned on Mercurial for the SourceForge project but I haven't done > anything with it yet, from the blurb on > https://sourceforge.net/scm/?type=hg&group_id=251339 and the documentation > at https://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial it looks > like SF does allow a project to create multiple repositories > > All committers should have full read/write access already if they want to > start playing with it. Is it worth us creating a scratch repository to > prototype the migration to Mercurial prior to importing into our default > "trunk" repository that SourceForge will point users to? > What do you mean by scratch repository? You mean what I suggested before that I would create a repository for the converted SVN elsewhere (probably Bitbucket) for review? By the way seeing that sourceforge doesn't work with multiple repos maybe for now it would be an overkill to split and stick to just having one. This isn't crucial and maybe I'm just getting ahead of myself. Could get a draft ready tomorrow. > >>By the way what software does the bugtracker run? > > > The tracker runs Bug Net (bugnetproject.com) - I just did an upgrade to > the latest version so I don't know if that will improve things for you at > all > Hurray! I guess the update did it and now the bugtracker works :) > > Rob > >> >>> >>> What do y'all think ? >>> >>> Cheers >>> >>> Kal >>> >>> On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...> >>> wrote: >>>> >>>> As you've all probably noticed I've been trying to grow the committers >>>> list lately because I don't want to have to do all the work myself nor >>>>do I >>>> need/want to review every minor patch. If someone has proved their >>>>ability >>>> by contributing over time I want to give them the opportunity to >>>>become more >>>> involved with the project if they desire. >>>> >>>> With this in mind we currently have the following committer invites >>>>open >>>> to Tomasz Pluskiewicz. >>>> >>>> I would also like to take the opportunity to invite Graham Moore (Kal's >>>> colleague at NetworkedPlanet) to become a committer if he too wishes, I >>>> should have done this when I invited Kal but it slipped my mind at the >>>>time. >>>> >>>> I have one/two other intermittent committers who I may approach >>>>privately >>>> off list first to see if they are still working actively with the >>>>project >>>> and if they are interested in joining as committers. If anyone else >>>>has >>>> potential committers in mind who they know have experience with the >>>>API and >>>> may like to get more involved suggestions are welcome >>>> >>>> Thanks, >>>> >>>> Rob >>>> >>>> >>>> >>>>------------------------------------------------------------------------ >>>>------ >>>> Live Security Virtual Conference >>>> Exclusive live event will cover all the ways today's security and >>>> threat landscape has changed and how IT managers can respond. >>>>Discussions >>>> will include endpoint security, mobile security and the latest in >>>>malware >>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>> >>> >>> >>> -- >>> Kal Ahmed >>> Director, Networked Planet Limited >>> e: kal...@ne... >>> w: www.networkedplanet.com >>> t: +44 1865 811131 >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. >>>Discussions >>> will include endpoint security, mobile security and the latest in >>>malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >>-------------------------------------------------------------------------- >>---- >>Live Security Virtual Conference >>Exclusive live event will cover all the ways today's security and >>threat landscape has changed and how IT managers can respond. Discussions >>will include endpoint security, mobile security and the latest in malware >>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-08-21 17:41:44
|
Kal Comments inline From: Kal Ahmed <ka...@ne...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Tuesday, August 21, 2012 12:59 AM To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: Re: [dotNetRDF-Develop] Open/Proposed Committer Invites > Hi Rob, > > Thanks for inviting us to join you on the project! I look forward to hopefully > making some useful contributions :) > > One thing I would be keen for us to discuss and agree is what procedures we > want to adopt as a group for dealing both with bugs and with feature requests > / extensions of the project. Its probably not possible to cover every > potential possibility but at least having some idea about whether it is OK to > go in a fix bugs from the list; what you should do if you find a bug and have > a patch (i.e. report it first or just patch it); and what to do about ideas > for extensions / features etc. > > In general I think it would work best if there is communication on this list, > even if it is just along the lines of "guys, I found this bug, did X to fix it > and I'm ready to commit" to give others a chance to explain why it is a > feature and not a bug :) For bigger things, I think a longer discussion would > probably be useful to make sure we are on the same page. Personally I tend to prefer the Apache style of CTR (commit then review) rather than the RTC (review than commit) style depending on what you are working on, we all have access to the repositories and the logs so we all can review other commits. On this point I would say please make sure you write descriptive commit messages, especially if your commit touches a lot of files. I always like being able to glance at the log and not have to dig into the actual diffs to know what changed. Related to this if you change/fix something try and remember to add it to the Change Log, there's a core library specific one under Libraries/core and a toolkit one under Utilities. I would agree that for new features and extensions it is sensible to have some degree of discussion on the list so we make sure everyone is in agreement on whether to add a feature/extension and how to go about it. However for bug fixes I would generally prefer that developers use their discretion. Make sure to write some unit test(s) that reproduce the bug, try to make a fix for the bug and check that your new tests pass AND that you haven't caused any existing tests to fail. If existing tests fail try to figure out why, in some cases it may be that the existing tests were silently assuming the old buggy behavior in which case fix those as well. If it isn't clear why the fix causes a regression elsewhere or you just aren't sure what the implications of making a change are then it would be sensible to start a discussion on the list before you commit. But if you can fix the bug and all the tests still pass then please go ahead and commit it. If we find out the fix causes other issues at a later point we can always revert or rework that commit as appropriate. I will be the first to admit that RDF/SPARQL etc can be somewhat arcane at times and I know me and Kal have gone back and forth on some thorny bugs in the past where one bug was hiding another bug and so it wasn't clear whether the behavior he was seeing was actually a bug or not. If in doubt ask, if you can fix it without introducing regressions fix it. Rob > > What do y'all think ? > > Cheers > > Kal > > On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...> > wrote: >> As you've all probably noticed I've been trying to grow the committers list >> lately because I don't want to have to do all the work myself nor do I >> need/want to review every minor patch. If someone has proved their ability >> by contributing over time I want to give them the opportunity to become more >> involved with the project if they desire. >> >> With this in mind we currently have the following committer invites open to >> Tomasz Pluskiewicz. >> >> I would also like to take the opportunity to invite Graham Moore (Kal's >> colleague at NetworkedPlanet) to become a committer if he too wishes, I >> should have done this when I invited Kal but it slipped my mind at the time. >> >> I have one/two other intermittent committers who I may approach privately off >> list first to see if they are still working actively with the project and if >> they are interested in joining as committers. If anyone else has potential >> committers in mind who they know have experience with the API and may like to >> get more involved suggestions are welcome >> >> Thanks, >> >> Rob >> >> ----------------------------------------------------------------------------->> - >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> > t: +44 1865 811131 > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the ways > today's security and threat landscape has changed and how IT managers can > respond. Discussions will include endpoint security, mobile security and the > latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_____________________ > __________________________ dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-08-21 17:30:10
|
Hey Tom Comments inline On 8/21/12 3:19 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi > >Thanks Rob for inviting me. I hope I will have an opportunity to >contribute soon enough. > >Now, I have some comments for Khal inline below. > >Regards, >Tom > >PS >Oh and you could start addressing me Tom. Tomasz seems awfully formal >to me anyway. > >On Tue, Aug 21, 2012 at 9:59 AM, Khalil Ahmed <ka...@ne...> >wrote: >> Hi Rob, >> >> Thanks for inviting us to join you on the project! I look forward to >> hopefully making some useful contributions :) >> >> One thing I would be keen for us to discuss and agree is what >>procedures we >> want to adopt as a group for dealing both with bugs and with feature >> requests / extensions of the project. Its probably not possible to cover >> every potential possibility but at least having some idea about whether >>it >> is OK to go in a fix bugs from the list; what you should do if you find >>a >> bug and have a patch (i.e. report it first or just patch it); and what >>to do >> about ideas for extensions / features etc. >> > >First I still cannot access the tracker (Chrome says >net::ERR_CONNECTION_RESET). This will be a problem. A quick Google search turned up http://support.google.com/chrome/bin/answer.py?hl=en&answer=117805 which is Chrome's support article about this error but not sure if it will be of any help > >Other than that I agree that this list is the current communication >platform and for now it is the best place to discuss our work. I have >also been thinking about http://www.uservoice.com/, which could be >open for people to suggest changes and vote on what other's have >suggested. This way we could track the actual demand for features. A >free plan should suffice for the time beeing. > >> >> In general I think it would work best if there is communication on this >> list, even if it is just along the lines of "guys, I found this bug, >>did X >> to fix it and I'm ready to commit" to give others a chance to explain >>why it >> is a feature and not a bug :) For bigger things, I think a longer >>discussion >> would probably be useful to make sure we are on the same page. >> > >As far as patching is concerned I think you will enjoy Mercurial. Not >sure how well SF integrates with it, but I think it treats it just as >SVN, which is a shame. With Bitbucket or Github there is an option to >fork, which creates a developer's personal copy of the repository >where he commits changes and the sends a pull request with information >what changed and which commits should get integrated with the main >branch. I have turned on Mercurial for the SourceForge project but I haven't done anything with it yet, from the blurb on https://sourceforge.net/scm/?type=hg&group_id=251339 and the documentation at https://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial it looks like SF does allow a project to create multiple repositories All committers should have full read/write access already if they want to start playing with it. Is it worth us creating a scratch repository to prototype the migration to Mercurial prior to importing into our default "trunk" repository that SourceForge will point users to? >By the way what software does the bugtracker run? The tracker runs Bug Net (bugnetproject.com) - I just did an upgrade to the latest version so I don't know if that will improve things for you at all Rob > >> >> What do y'all think ? >> >> Cheers >> >> Kal >> >> On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...> >> wrote: >>> >>> As you've all probably noticed I've been trying to grow the committers >>> list lately because I don't want to have to do all the work myself nor >>>do I >>> need/want to review every minor patch. If someone has proved their >>>ability >>> by contributing over time I want to give them the opportunity to >>>become more >>> involved with the project if they desire. >>> >>> With this in mind we currently have the following committer invites >>>open >>> to Tomasz Pluskiewicz. >>> >>> I would also like to take the opportunity to invite Graham Moore (Kal's >>> colleague at NetworkedPlanet) to become a committer if he too wishes, I >>> should have done this when I invited Kal but it slipped my mind at the >>>time. >>> >>> I have one/two other intermittent committers who I may approach >>>privately >>> off list first to see if they are still working actively with the >>>project >>> and if they are interested in joining as committers. If anyone else >>>has >>> potential committers in mind who they know have experience with the >>>API and >>> may like to get more involved suggestions are welcome >>> >>> Thanks, >>> >>> Rob >>> >>> >>> >>>------------------------------------------------------------------------ >>>------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. >>>Discussions >>> will include endpoint security, mobile security and the latest in >>>malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >> >> >> -- >> Kal Ahmed >> Director, Networked Planet Limited >> e: kal...@ne... >> w: www.networkedplanet.com >> t: +44 1865 811131 >> >> >>------------------------------------------------------------------------- >>----- >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >>Discussions >> will include endpoint security, mobile security and the latest in >>malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Live Security Virtual Conference >Exclusive live event will cover all the ways today's security and >threat landscape has changed and how IT managers can respond. Discussions >will include endpoint security, mobile security and the latest in malware >threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2012-08-21 10:20:07
|
Hi Thanks Rob for inviting me. I hope I will have an opportunity to contribute soon enough. Now, I have some comments for Khal inline below. Regards, Tom PS Oh and you could start addressing me Tom. Tomasz seems awfully formal to me anyway. On Tue, Aug 21, 2012 at 9:59 AM, Khalil Ahmed <ka...@ne...> wrote: > Hi Rob, > > Thanks for inviting us to join you on the project! I look forward to > hopefully making some useful contributions :) > > One thing I would be keen for us to discuss and agree is what procedures we > want to adopt as a group for dealing both with bugs and with feature > requests / extensions of the project. Its probably not possible to cover > every potential possibility but at least having some idea about whether it > is OK to go in a fix bugs from the list; what you should do if you find a > bug and have a patch (i.e. report it first or just patch it); and what to do > about ideas for extensions / features etc. > First I still cannot access the tracker (Chrome says net::ERR_CONNECTION_RESET). This will be a problem. Other than that I agree that this list is the current communication platform and for now it is the best place to discuss our work. I have also been thinking about http://www.uservoice.com/, which could be open for people to suggest changes and vote on what other's have suggested. This way we could track the actual demand for features. A free plan should suffice for the time beeing. > > In general I think it would work best if there is communication on this > list, even if it is just along the lines of "guys, I found this bug, did X > to fix it and I'm ready to commit" to give others a chance to explain why it > is a feature and not a bug :) For bigger things, I think a longer discussion > would probably be useful to make sure we are on the same page. > As far as patching is concerned I think you will enjoy Mercurial. Not sure how well SF integrates with it, but I think it treats it just as SVN, which is a shame. With Bitbucket or Github there is an option to fork, which creates a developer's personal copy of the repository where he commits changes and the sends a pull request with information what changed and which commits should get integrated with the main branch. By the way what software does the bugtracker run? > > What do y'all think ? > > Cheers > > Kal > > On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...> > wrote: >> >> As you've all probably noticed I've been trying to grow the committers >> list lately because I don't want to have to do all the work myself nor do I >> need/want to review every minor patch. If someone has proved their ability >> by contributing over time I want to give them the opportunity to become more >> involved with the project if they desire. >> >> With this in mind we currently have the following committer invites open >> to Tomasz Pluskiewicz. >> >> I would also like to take the opportunity to invite Graham Moore (Kal's >> colleague at NetworkedPlanet) to become a committer if he too wishes, I >> should have done this when I invited Kal but it slipped my mind at the time. >> >> I have one/two other intermittent committers who I may approach privately >> off list first to see if they are still working actively with the project >> and if they are interested in joining as committers. If anyone else has >> potential committers in mind who they know have experience with the API and >> may like to get more involved suggestions are welcome >> >> Thanks, >> >> Rob >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > t: +44 1865 811131 > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Khalil A. <ka...@ne...> - 2012-08-21 07:59:49
|
Hi Rob, Thanks for inviting us to join you on the project! I look forward to hopefully making some useful contributions :) One thing I would be keen for us to discuss and agree is what procedures we want to adopt as a group for dealing both with bugs and with feature requests / extensions of the project. Its probably not possible to cover every potential possibility but at least having some idea about whether it is OK to go in a fix bugs from the list; what you should do if you find a bug and have a patch (i.e. report it first or just patch it); and what to do about ideas for extensions / features etc. In general I think it would work best if there is communication on this list, even if it is just along the lines of "guys, I found this bug, did X to fix it and I'm ready to commit" to give others a chance to explain why it is a feature and not a bug :) For bigger things, I think a longer discussion would probably be useful to make sure we are on the same page. What do y'all think ? Cheers Kal On Mon, Aug 20, 2012 at 10:10 PM, Rob Vesse <rv...@vd...>wrote: > As you've all probably noticed I've been trying to grow the committers > list lately because I don't want to have to do all the work myself nor do I > need/want to review every minor patch. If someone has proved their ability > by contributing over time I want to give them the opportunity to become > more involved with the project if they desire. > > With this in mind we currently have the following committer invites open > to Tomasz Pluskiewicz. > > I would also like to take the opportunity to invite Graham Moore (Kal's > colleague at NetworkedPlanet) to become a committer if he too wishes, I > should have done this when I invited Kal but it slipped my mind at the time. > > I have one/two other intermittent committers who I may approach privately > off list first to see if they are still working actively with the project > and if they are interested in joining as committers. If anyone else has > potential committers in mind who they know have experience with the API and > may like to get more involved suggestions are welcome > > Thanks, > > Rob > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com t: +44 1865 811131 |
|
From: Rob V. <rv...@vd...> - 2012-08-20 21:41:56
|
As you've all probably noticed I've been trying to grow the committers list lately because I don't want to have to do all the work myself nor do I need/want to review every minor patch. If someone has proved their ability by contributing over time I want to give them the opportunity to become more involved with the project if they desire. With this in mind we currently have the following committer invites open to Tomasz Pluskiewicz. I would also like to take the opportunity to invite Graham Moore (Kal's colleague at NetworkedPlanet) to become a committer if he too wishes, I should have done this when I invited Kal but it slipped my mind at the time. I have one/two other intermittent committers who I may approach privately off list first to see if they are still working actively with the project and if they are interested in joining as committers. If anyone else has potential committers in mind who they know have experience with the API and may like to get more involved suggestions are welcome Thanks, Rob |
|
From: Rob V. <rv...@vd...> - 2012-08-20 21:37:29
|
Hi All Currently we have brief bios of myself and Ron on the Project Homepage, what I would like to do is change those to be simple 1 line statements of the form "X works as Job Title at Company" and then link to a separate developer bios page where we could put more information about each developer and their contributions to the project and other interests e.g. side-projects, commercial work with dotNetRDF or otherwise etc. If you'd like a more interesting bio than the one I will write up for you later this week which will likely just summarize who you are, company you work for and your involvement in the project then please send me a quick bio in reply to this email. Rob |
|
From: Rob V. <rv...@do...> - 2012-08-20 20:57:16
|
All I have been through Trunk and GZipped up some of the big data files that are mostly culprit for the large check out size since these days we can read them direct from GZip in the places we need them, Trunk should be around 300MB slimmer now Hope this helps Rob |
|
From: Tomasz P. <tom...@gm...> - 2012-08-20 16:47:23
|
Hi I am actually working on this roght now in my spare time. Unfortunately it is a trial and error work and each attempt is quite time consuming. I am trying to convert the repository with branches and tags intact and getting it done will require some manual mapping of relevant commits to recreate the branch/merge paths. There is however one issue I'm not sure I will be able to overcome. The conversion should be done sccording to the current structure of branches, tags (releaces) and trunk. It seem to work fine but because earlier in the repository's history, the basic layout was diffrent and the migrated Mercurial history starts with the "Reorganizing repository". That is around version 0.4. Thus it will be vital to retain the SVN read-only for reference. This is what most projects I've seen migrate do anyway. In my opinion we could remake the repository into smaller ones: Core (most of the current trunk) Utilities (the big stuff there and probably most committers-to-be won't really need to go there at first) Documentation (this sits outside of trunk anyways now) Last but not least we could have a build repository with the release build scripts, nightlies and the other repos as subrepositories). Have a look here: http://mercurial.selenic.com/wiki/Subrepository#Use_a_thin_shell_repository_to_manage_your_subrepositories I should have it done in the next days and when I'm done I will create a temp account on bitbucket for you to see how you feel about it. Regards, Tomasz On Mon, Aug 20, 2012 at 6:30 PM, Rob Vesse <rv...@do...> wrote: > As I said previously I am also willing to give this a go, I just haven't had > the time to sit down and do this and as I said before we prefer to do this > at the end of a release cycle so I'm not at risk of affecting any > in-progress code > > I will look at getting this done after the next release. If you have input > on how best to migrate the current structure into Mercurial that would be > appreciated, I would suggest not moving the releases/ tree of the > branches/obsolete/ tree as we can still point people who care back to SVN > for those. > > It is likely that we can reduce the size of branches and Trunk if we were to > GZip certain large data files that are present. I will look at trying to do > this fairly soon > > Rob > > From: Tomasz Pluskiewicz <tom...@gm...> > Reply-To: dotNetRDF Developer Discussion and Feature Request > <dot...@li...> > Date: Thursday, August 16, 2012 11:13 AM > To: dotNetRDF Developer Discussion and Feature Request > <dot...@li...> > Subject: Re: [dotNetRDF-Develop] Patches for Silverlight/Windows Phone > builds > > Hi > > I think it is a good opportunity to again suggest moving the source code to > a distributed VCS like Mercurial or Git. It would be very much easier to > submit and accept patches which, I believe, would also encourage new > commitments as more and more users are acquainted with distributed version > control systems. > > Another reason I am coming up with this again is because I recently tried to > check out the repository on slower connections. The repository is quite big > and on slow connection it is not possible to check out all of it. And with a > faster connection it takes a very long time. There are quite a few projects > in all in one repository and the development process will benefit from > splitting it into smaller ones as would be done with Git/Hg. I don't know > what your experience is but there should also be a performance boost. > > I noticed the problem with size is probably due to how Subversion handles > tagging. Now there is a "tag" for quite a few releases, which was fine until > 050, but all later tags weigh 480+ MB, most of it duplicate or little > changed files in the Utilities subfolders. The thing is in SVN tag and > branch are virtually the same thing, while in Hg (not sure about Git > exactly) tag is just a pair of label and the corresponding commit, for > easier navigation in the commit tree. > > I could try converting the repository to hg and splitting it into smaller > pieces as an experiment and upload temporarily to some free hosting for your > review when I'm done. > > I am also interested in the opinion of other potential committers. Kal, what > do you think? Is it worth the effort? > > Regards, > Tomasz > > On Wed, Aug 15, 2012 at 7:17 PM, Rob Vesse <rv...@do...> wrote: >> Thanks for the patches, I was aware of this failures but hadn't got round >> to >> fixing them yet >> >> Patches applied as of revision 2370 >> >> Would you be interested in joining the project as a committer such that >> you >> would be able to apply fixes like this yourself directly to the codebase >> without having to wait for me to get round to checking them over? This >> would also make it easier if you have spare cycles to look at and perhaps >> fix pressing issues like the XML encoding ones Graham recently reported >> when >> I don't have the time to get to them immediately >> >> If you are interested let me know and I can get you set up with commit >> access >> >> Thanks, >> >> Rob >> >> From: Kal Ahmed <ka...@ne...> >> Reply-To: dotNetRDF Developer Discussion and Feature Request >> <dot...@li...> >> Date: Monday, August 13, 2012 7:03 AM >> To: <dot...@li...> >> Subject: [dotNetRDF-Develop] Patches for Silverlight/Windows Phone builds >> >> Hi, >> >> I ran into a couple of problems building the core.windowsphone library >> (from >> rev 2369 in Trunk) and have created patches for them. >> >> >> 2369_20120813_libraries_core.silverlight_compatibility_SilverlightCompatability.cs.patch >> Adds FindIndex<T>(Predicate<T>) method to the List<T> class as an >> extension >> method (this method is present in .NET 4.0 but not in the Silverlight >> libraries) >> >> 2369_20120813_libraries_core_query_SparqlOperator.cs.patch >> Windows Phone libraries do not provide Enum.GetValues(Type) so an >> alternative way of iterating the values of SparqlOperatorType enum is >> required. I can't see a way to get the values at runtime, so I've added a >> static array of SparqlOperatorType enum values and conditionally compiled >> code for WindowsPhone that iterates that array rather than trying to call >> Enum.GetValues. >> >> Cheers >> >> Kal >> -- >> Kal Ahmed >> Director, Networked Planet Limited >> e: kal...@ne... >> w: www.networkedplanet.com >> t: +44 1865 811131 >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference Exclusive live event will cover all the >> ways today's security and threat landscape has changed and how IT managers >> can respond. Discussions will include endpoint security, mobile security >> and >> the latest in malware threats. >> >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ >> dotNetRDF-develop mailing list dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the > ways today's security and threat landscape has changed and how IT managers > can respond. Discussions will include endpoint security, mobile security and > the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > dotNetRDF-develop mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2012-08-20 16:31:07
|
As I said previously I am also willing to give this a go, I just haven't had the time to sit down and do this and as I said before we prefer to do this at the end of a release cycle so I'm not at risk of affecting any in-progress code I will look at getting this done after the next release. If you have input on how best to migrate the current structure into Mercurial that would be appreciated, I would suggest not moving the releases/ tree of the branches/obsolete/ tree as we can still point people who care back to SVN for those. It is likely that we can reduce the size of branches and Trunk if we were to GZip certain large data files that are present. I will look at trying to do this fairly soon Rob From: Tomasz Pluskiewicz <tom...@gm...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Thursday, August 16, 2012 11:13 AM To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: Re: [dotNetRDF-Develop] Patches for Silverlight/Windows Phone builds > > Hi > > I think it is a good opportunity to again suggest moving the source code to a > distributed VCS like Mercurial or Git. It would be very much easier to submit > and accept patches which, I believe, would also encourage new commitments as > more and more users are acquainted with distributed version control systems. > > Another reason I am coming up with this again is because I recently tried to > check out the repository on slower connections. The repository is quite big > and on slow connection it is not possible to check out all of it. And with a > faster connection it takes a very long time. There are quite a few projects in > all in one repository and the development process will benefit from splitting > it into smaller ones as would be done with Git/Hg. I don't know what your > experience is but there should also be a performance boost. > > I noticed the problem with size is probably due to how Subversion handles > tagging. Now there is a "tag" for quite a few releases, which was fine until > 050, but all later tags weigh 480+ MB, most of it duplicate or little changed > files in the Utilities subfolders. The thing is in SVN tag and branch are > virtually the same thing, while in Hg (not sure about Git exactly) tag is just > a pair of label and the corresponding commit, for easier navigation in the > commit tree. > > I could try converting the repository to hg and splitting it into smaller > pieces as an experiment and upload temporarily to some free hosting for your > review when I'm done. > > I am also interested in the opinion of other potential committers. Kal, what > do you think? Is it worth the effort? > > Regards, > Tomasz > > On Wed, Aug 15, 2012 at 7:17 PM, Rob Vesse <rv...@do...> wrote: >> > Thanks for the patches, I was aware of this failures but hadn't got round >> to >> > fixing them yet >> > >> > Patches applied as of revision 2370 >> > >> > Would you be interested in joining the project as a committer such that you >> > would be able to apply fixes like this yourself directly to the codebase >> > without having to wait for me to get round to checking them over? This >> > would also make it easier if you have spare cycles to look at and perhaps >> > fix pressing issues like the XML encoding ones Graham recently reported >> when >> > I don't have the time to get to them immediately >> > >> > If you are interested let me know and I can get you set up with commit >> > access >> > >> > Thanks, >> > >> > Rob >> > >> > From: Kal Ahmed <ka...@ne...> >> > Reply-To: dotNetRDF Developer Discussion and Feature Request >> > <dot...@li...> >> > Date: Monday, August 13, 2012 7:03 AM >> > To: <dot...@li...> >> > Subject: [dotNetRDF-Develop] Patches for Silverlight/Windows Phone builds >> > >> > Hi, >> > >> > I ran into a couple of problems building the core.windowsphone library >> (from >> > rev 2369 in Trunk) and have created patches for them. >> > >> > >> 2369_20120813_libraries_core.silverlight_compatibility_SilverlightCompatabili >> ty.cs.patch >> > Adds FindIndex<T>(Predicate<T>) method to the List<T> class as an extension >> > method (this method is present in .NET 4.0 but not in the Silverlight >> > libraries) >> > >> > 2369_20120813_libraries_core_query_SparqlOperator.cs.patch >> > Windows Phone libraries do not provide Enum.GetValues(Type) so an >> > alternative way of iterating the values of SparqlOperatorType enum is >> > required. I can't see a way to get the values at runtime, so I've added a >> > static array of SparqlOperatorType enum values and conditionally compiled >> > code for WindowsPhone that iterates that array rather than trying to call >> > Enum.GetValues. >> > >> > Cheers >> > >> > Kal >> > -- >> > Kal Ahmed >> > Director, Networked Planet Limited >> > e: kal...@ne... >> > w: www.networkedplanet.com <http://www.networkedplanet.com> >> > t: +44 1865 811131 >> > >> ------------------------------------------------------------------------------ >> > Live Security Virtual Conference Exclusive live event will cover all the >> > ways today's security and threat landscape has changed and how IT managers >> > can respond. Discussions will include endpoint security, mobile security >> and >> > the latest in malware threats. >> > >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/____________________ >> ___________________________ >> > dotNetRDF-develop mailing list dot...@li... >> > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Live Security Virtual Conference >> > Exclusive live event will cover all the ways today's security and >> > threat landscape has changed and how IT managers can respond. Discussions >> > will include endpoint security, mobile security and the latest in malware >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> > _______________________________________________ >> > dotNetRDF-develop mailing list >> > dot...@li... >> > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference Exclusive live event will cover all the ways > today's security and threat landscape has changed and how IT managers can > respond. Discussions will include endpoint security, mobile security and the > latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_____________________ > __________________________ dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
48 messages has been excluded from this view by a project administrator.
