meta user
network profile
| bio | website | itaccess.org |
|---|---|---|
| location | Addis Ababa, Ethiopia | |
| age | 32 | |
| visits | member for | 2 years, 3 months |
| seen | Jun 4 at 13:01 | |
| stats | profile views | 120 |
|
Mar 29 |
comment |
Distributed Issue Tracking @WyattBarnett it is hard to speculate how people would react to a well formed tool. Perhaps they would be more likely to submit issues if it were possible to do offline, and without connection/explicitly logging in. Perhaps people who submit issues online would end up delaying their postings if it was available offline. My intuition, is that if it is made extremely simple to push, people will do it frequently, because if they have created an issue, they will want the world to see it. |
|
Mar 29 |
comment |
Distributed Issue Tracking is that concern rooted in the problem of sifting through irrelevant data? or from the point of view of storage space? |
|
Mar 29 |
comment |
Sell software to the world Sounds fair - has anything like that ever happened - via kickstart, or any similar crowd funding method? |
|
Mar 29 |
comment |
Sell software to the world That is what I am asking - can the current owner release the rights, after a kickstart project successfully gathers the desired funds. Is it technically possible? I am talking patent protected tech. |
|
Mar 29 |
comment |
Distributed Issue Tracking To me it makes most sense to include the issues in the project VCS, so that all issues are available, and it is a problem of reporting to extract the relevant ones. I think the overhead on the repo is acceptable, what do you think? As for a central server, I imagine a system after git, where it is in it's implementation, totally distributed, but you are free to host it on a server you call the central one (like github for example). Any thoughts? |
|
Mar 29 |
asked | Sell software to the world |
|
Mar 29 |
comment |
Distributed Issue Tracking @WyattBarnett that is a valid concern, perhaps mitigated by behavioural patterns, and perhaps software. Personally I see the only difference between a blog and a website is how often you update it, is it not the same for distributed issue tracking? If you update it often, it is the same as checking a web-page of issues often no? The only danger is people not updating, and submitting issue often, but so long as there is a one-click solution, it is not a problem right? I understand that this need for connectivity is in conflict with one of the large benefits of distributed issue tracking. |
|
Mar 29 |
asked | Distributed Issue Tracking |
|
Feb 25 |
awarded | Caucus |
|
Feb 25 |
awarded | Constituent |
|
Oct 11 |
awarded | Citizen Patrol |
|
Feb 8 |
comment |
Localised programming languages that is pretty awesome |
|
Feb 8 |
asked | Localised programming languages |
|
Feb 7 |
accepted | How do I share my jQuery plugin with the world? |
|
Feb 7 |
asked | How do I share my jQuery plugin with the world? |
|
Oct 24 |
awarded | Editor |
|
Oct 24 |
revised |
My boss wants a narrated line-by-line English explanation of our code added 606 characters in body |
|
Sep 17 |
awarded | Famous Question |
|
Sep 8 |
awarded | Favorite Question |
|
Sep 7 |
awarded | Great Question |
