... | ... | @@ -6,9 +6,9 @@ The current purpose I have in mind for this wiki is simply to outline the projec |
|
|
|
|
|
I am brand new to github, so I'm still learning to make use of all the tools offered here and welcome guidance and insight on any issues, and for the most part I am not really interested in being the project lead here as I am not experienced in this area. However I do think I have developed quite a vision for this project and that I am capable of playing a leadership role to a degree and will of course do my best until someone else comes along. On that note I'd like to try keep all aspects of this project accessible and workable by others as I have a history of being an unreliably whimsical digital nomad, and I want to see this project come to realization even if I should become scarce.
|
|
|
|
|
|
I've been tossing this idea out, mostly in #debian and #debian-offtopic on freenode from time to time as issues arose for probably a decade or so now, and never even got any responses one way or another. Recently someone finally took interest and seconded the idea, and annadane and I have taken steps to create and promote the idea to garner more interest. I have been very surprised by the level of response that we've gotten so quickly. Within the first 24 hours after announcing the project and creating a github account, we had half a dozen people in the development channel, a log bot setup, and were already discussing seriously how to make this project a reality. I am proud to say that these pioneers of the project were not just passersby but have stuck around and continued to contribute their thoughts and skills and that we're well on our way to building a development team to redesign the support model for our beloved OS.
|
|
|
I've been tossing this idea out, mostly in #debian and #debian-offtopic on freenode from time to time as issues arose for probably a decade or so now, and never even got any responses one way or another. Recently someone finally took interest and seconded the idea, and annadane and I have taken steps to create and promote the idea to garner more interest. I have been very surprised by the level of response that we've gotten so quickly. Within the first 24 hours after announcing the project and creating a github account, we had half a dozen people in the development channel, a log bot setup, and we're already discussing seriously how to make this project a reality. I am proud to say that these pioneers of the project were not just passersby but have stuck around and continued to contribute their thoughts and skills and that we're well on our way to building a development team to redesign the support model for our beloved OS.
|
|
|
|
|
|
The problems we face right now are many, not the least of which is that my vision and the sorts of things we have all observed as issues with the status quo of our support systems, are not well documented and clearly outlined for interested parties to wrap their heads around what we're trying to do and why. I hope this wiki will address that issue at least. The next in line of our many problems is of course need of hands to do the work. Currently we don't have any regular coders with experience taking on a project of this magnitude. I can code python, but my experience is limited to a handful or so modules, and mostly small tools to automate day-to-day tasks for myself, I have not participated in any large FOSS project before other than dabbling with hedgewars where I mostly wrote a few scripts, contributed some ideas, and created my own clone of their source tree which I mostly broke horribly trying to learn to fix some things that were bugging me. heh. I certainly have never lead a software project before. My co-founder, a confessed reddit addict, has absolutely no programming experience or skill at this point and is learning from scratch. Among the others now hanging out in the development channel, we have a network engineer who mostly writes tools in C and Java, who is also just learning python, and a couple other people with similar limited programming experience. What I am saying is this, we can use the help and guidance of real programmers, especially those familiar with designing web service APIs, trust based systems, GUI, and working on projects with a lot of moving parts, and lofty goals which include integration with many existing systems whose developers and volunteer supporters we want to work with as synergistically as possible without offending them by implying their systems are not effective or inconveniencing them in any way by pushing these changes upon them.
|
|
|
The problems we face right now are many, not the least of which is that my vision and the sorts of things we have all observed as issues with the status quo of our support systems, are not well documented and clearly outlined for interested parties to wrap their heads around what we're trying to do and why. I hope this wiki will address that issue at least. The next in line of our many problems is of course need of hands to do the work. Currently we don't have any regular coders with experience taking on a project of this magnitude. I can code python, but my experience is limited to a handful or so modules, and mostly small tools to automate day-to-day tasks for myself, I have not participated in any large FOSS project before other than dabbling with hedgewars where I mostly wrote a few scripts, contributed some ideas, and created my own clone of their source tree which I mostly broke horribly trying to learn to fix some things that were bugging me. heh. I certainly have never lead a software project before. My co-founder, a confessed Reddit addict, has absolutely no programming experience or skill at this point and is learning from scratch. Among the others now hanging out in the development channel, we have a network engineer who mostly writes tools in C and Java, who is also just learning python, and a couple other people with similar limited programming experience. What I am saying is this, we can use the help and guidance of real programmers, especially those familiar with designing web service APIs, trust based systems, GUI, and working on projects with a lot of moving parts, and lofty goals which include integration with many existing systems whose developers and volunteer supporters we want to work with as synergistically as possible without offending them by implying their systems are not effective or inconveniencing them in any way by pushing these changes upon them.
|
|
|
|
|
|
These changes should come about as more in addition to, but not instead of the existing systems, and should integrate as unobtrusively as can be, as an additional resource unifying our existing resources and making them easier to use, and not interfere with business as usual.
|
|
|
|
... | ... | @@ -26,8 +26,8 @@ if'm for not only relinquishing #diss, where he'd been squatting, to the project |
|
|
|
|
|
zellkou for taking the initiative of setting up disslogbot and offering server support for our needs at this early phase of the project.
|
|
|
|
|
|
our other regulars in #diss, sdk, DerLGm, MagicFab for hanging around and giving their input.
|
|
|
Our other regulars in #diss, sdk, DerLGm, MagicFab for hanging around and giving their input.
|
|
|
|
|
|
all our stargazers and watchers here on github for taking an interest.
|
|
|
All our stargazers and watchers here on github for taking an interest.
|
|
|
|
|
|
and everyone who responded to the posts on reddit and Debian wiki, even those who are naysayers and post hijackers, because there is no such thing as bad press, and negative opinions are just as valuable and serve to help identify other issues we will want to address. |
|
|
\ No newline at end of file |
|
|
And everyone who responded to the posts on Reddit and Debian wiki, even those who are naysayers and post hijackers, because there is no such thing as bad press, and negative opinions are just as valuable and serve to help identify other issues we will want to address. |
|
|
\ No newline at end of file |