Maka Si Tomni (Surround The Universe)
Bringing Forth a Thriving Lakota Language & Culture
Maka Si Tomni - Surrounding the Universe Bringing Forth a Thriving Lakota Language & Culture Little Big Horn Victory Celebration, June 25th 2008 is Sovereignty-In-Action - a spiritual, educational and cultural celebration of 1st nation peoples at Little Big Horn National Monument, Montana USA. This June 2008 event is the largest gathering of descendants ...learn more
GROUP DETAILS
Created: Feb 18, 2008
Updated: Sep 21, 2009
Membership: Open
Semi-Private
Issue Tracking System
I have received multiple concerns from other members about the direction of WE. This points to holes in the design of the platform--that people have to complain, either because there are real issues not being addressed or the platform doesn't have appropriate ways for them to resolve their issues.
An issue tracking system on WE would improve the productivity of our interactions. I always install one on client sites that interact with the world at large because it makes for much happier users. Dropping issues in a blog like this just doesn't allow for effective collaboration. It is necessary to build a system so that issues get resolved in a timely and efficient manner and that the most appropriate parties are given opportunity to respond. For example, I'm almost certain that whoever reads this will have to spend valuable time hunting down appropriate people on the WE team to respond to various parts of this post, when with the right system in place, it could be handled auto magically, including the ability to run reports.
~by Michael D. Alexander (mdajobs)
Comments (1 - 10 of 10)
|
|
|
Your welcome Bowo.
Re working within the limitations of the present system, that is what I've been doing. The only other choice is not to give it energy, i.e., not participate. Is this what you mean?
Perhaps you can assist me further. I would like to check on the other threads I started re areas of focus, transparency and making WE project rather than interest based. Can you tell me how to view a list of all threads I've started here at WE since becoming a member?
Lastly, is there a way to view a history of email exchanges here with other WE members and staff?
Thank you in advance,
Michael D. Alexander |
|
Thank you Michael,
The idea of a robust issue tracking system is in our mind already. We will definitely be in contact should we need feedback on "evolving this platform to a more usable state" (and believe me, we do need feedback from people like you).
Perhaps, other than the absence of an issue tracking system, you readily have some other feedback to share? If you're willing to operate within the limitations of our current system of course...
Thanks again, Bowo |
|
|
Hello everyone and thank you for chiming in.
I wish to extend my apologies for a long absense and dropping the ball on this thread I started over four months ago.
By "issue", I mean anything. I trust that a user who wishes to post a "suggestion" or "idea" has an ISSUE with the way things are NOW and wants to see a CHANGE.
While I'm not attached to the term "issue", issue tracking and issue tracking software is a well established field. Therefore, I see comments re "what to call it" as off point and a distraction. Same comment for multiple systems--very unproductive. The "type" of issue can be selected from a drop down list box.
The main point as I see it is to provide users at WE a way to move from issue/suggestion/idea/etc. to solution as quickly as possible. This means leveraging technology and brilliant design to the max that is not being done here at WE.
My bread and butter is designing high performance web applications for my customers. It would be embarassing for me to authorize functionality like much of what I see here here at WE. It is archaic and unproductive.
So, if any of you can broker a serious conversation with development re how to evolve this platform to a more usable state, I'm willing to throw in my support. Otherwise, I'm out of words on this thread and don't know how to be more clear.
Regards,
Michael D. Alexander
|
|
|
@Michael: Thanks for stopping by. Looking forward to hear your ideas. |
|
Hi -I'll have a little more time for positive discourse on these matters in 2-3 weeks, but wanted to let you all know I am tracking. I don't know if I'd frame my stance as pertaining to issues/concerns or just ideas, suggestions and invitations to new approaches that may not require dramatic first steps (i.e. should be easy to set in motion for first steps). Much of my thought is bound up in what I am calling a "Solutions Ecology" (with due credit to Ellison Horne).
We, together, have to embody this new way of working together, and inviting others to build together in a lasting and respectful manner. |
|
Seems to me what I'm hearing is that their are two systems being discussed:
(1) Suggestions / Help Desk / Technical Fixes - which related to the platform and responsiveness to help requests
(2) Solving Issues relating to Social Justice and Environmental Restoration - more the usability of the site to support the movement. This has been described in part in previous suggestions as 'Needs/Wants' matching service.
Are we agreed or not that (1) functions tolerably well and (2) needs more work? If so what ideas are out there? |
|
|
Hello Michael,
Very well. So it seems I'm missing this 'huge' thing called "issue tracking system". Just did a quick browse through on the wikipedia link you supplied, and done some quick googling. I think I understand better now where you're coming from.
But first, some clarification of terms. I believe what you're suggesting with the word 'issue' is everything related to the development of WE (platform/software, user interface, non-technical issues, etc.) and how an "issue tracking system" would help smooth things out for everyone. Is this correct? Then, there's another kind of 'critical issues' you mentioned in your comment below, which is the "poverty, war, environmental degradation" kind of issues. I'm guessing that you're not proposing the use of an "issue tracking system" for these? But I can be wrong!...and it would indeed be interesting how any "issue tracking system" can be implemented to sort stuff like that out.
Second, yes indeed, we do have different expectations and criteria for "what works". Since yours appear to be higher (coming from an experienced background), I am happy to follow your lead on this. How do you foresee we reconfigure our current community support system and then replace them with an issue tracking system? How do we integrate the issue tracking system with the WE platform? Do you have an example from your past work of system(s) that could fit well with WE? What are the costs associated with this move?
Third, I think our tech team is using such tracking system for all software aspects of the WE platform (bugs, new feature development, testing, etc.). Basically we listen to all community feedback and suggestions via all channels we set up (listed in my previous comment) and then transfer everything software-related to the issue tracking system. I'm seeing it working ok from my end, given our limited technical resources and the need to prioritize resolving some issues over others.
Fourth, I am well aware of Janine's excellent observations (in fact, behind the screen, I was the one that 'indirectly' ignited that to come out :) Always good to hear direct , honest and reasonable feedback. Just like yours here). We're taking good note of her feedback and are working on some things to alleviate some of the problems she pointed out. If you need to see some of the more positive side of WE, please visit the testimonials and success stories page (well... by definition, it contains only the positives... and probably does not meet your high expectations... but it's a start!). All in all, WE is a work in progress, there lots to do and so little time/resources. That's why we're always happy if the WE community members (like you) is willing to invest their time, energy and expertise to take WE forward. I'm also inviting Michael, Eve and Vic to join us here. It would be interesting to hear what they have to say.
So, I look forward to hear your response and do let me know if I missed anything.
Regards, Bowo |
|
|
Happy Wednesday Bowo. Re present resources working, I'm new here and will defer to you on that one until I get more experience.
Judging by the difficulties I've had getting responses, comments I've heard, the state of the areas of focus, and lack of an issue tracking system, we may just have different expectations and criteria for "what works".
My read is that web collaboration is all about connecting the right people and data as quickly as possible to produce a desired result in shifting consciousness and actions. That's why I'm suggesting a project focus and better communication in the form of an Issue Tracking System, so WE can do what it does even better. Considering how critical the issues are facing us, working "pretty well", is likely to be sub-optimal.
You might also consider that there is a difference between those of us that have a lot of time on their hands and those that
lead exceptionally busy lives. Speaking for myself, the time to get things done is a critical factor in order for me to be feel
productive and that my time is being well spent. Janine's 17 month snap shot of her experiences here (below) isn't exactly
inspiring. For the time being, I'm hanging in there and looking to see if this is a productive place for me to be. Does WE
track statistics for retention here? Re examples, take your pick:
http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
Re concerns, I've posted mine. Re other's, please follow up with Michael Maranda, Eve Libertone and Janine the editor. See Janine's post, "Are We Making the Best Use of Wiser Earth", here: http://www.wiserearth.org/article/cc6ca36b36163cac47dd11373138d15b
Vic Desotelle might also have some insights for you. Catch Vic here on WE and also at:
http://discoveryfuel.ning.com/. Regards. |
|
|
Can you provide specific examples of what you mean by 'issue' here? Do you have some examples too on "issue tracking system" out there?
As you've probably realized, our system on responding to the community basically are:
These are working pretty well for us so far.
Out of curiosity, what "multiple concerns" were you hearing? |
Dear Bowo,
I just reread your long response to my earlier query and would like to take this opportunity to address your questions, since I haven't done that yet.
Re how to change the present system. Except for the question on what to include in issue tracking, that I've already dealt with, the rest are issues of design that I can only comment on after I have had the opportunity to review it. To date, I haven't had the opportunity to learn any details about your system technology. Whereas I have received an email from your lead developer I have not heard back from him. My absence may have something to do with this.
All of my projects are Java based. I use JavaServer Faces, a component technology similar to Microsoft WebForms combined with the Java Swing API, that renders in the browser and has hooks into the JavaScript model. One can literally create any kind of user interface functionality with this technology. In addition, the Java API is staggering. Anything you can dream up from instrumenting performance of the Java Virtual Machine (Java interpreter) to making distributed method calls across the Internet. The Java APIs span the gamut from MIDI to asynchrounous messaging between applications and legacy ERP systems.
All my projects are UML driven. I don't allow any code to be written without it being synchronized with the model. This prevents misguided coding with the advantage that anyone that speaks UML can review our architecture in all its gory details.
I know that your technology is not leveraging partial page refreshes (a profoundly great idea), so apparently your not using ASP.NET.
I presume this is way over your head and please understand how unproductive it is to attempt a conversation with one who is unprepared to have that conversation.
In summary, what you have asked is effectively the same as going to a doctor that speaks a language you don't understand, and asking the doctor to diagnose a patient without the patent being in the room.
A solution to your problem would involve the following elements, regardless of where you are now:
1. A transparent WE. Right now the controllers and managers of the technology sit behind a wall. If I want to get messages to them I have to talk to someone who doesn't speak my language, who then throws messages over the wall. How anyone in management thinks this productive is beyond me. This is classic, old school command and control paradigm. If you don't have organization and responsibility flow charts accessible by the membership, you're pretty far from transparency.
2. Select the best technology for Web Application Development
3. Creat an open source community collaboration on your platform design and coding so anyone can see what you're doing and contribute.
4. Mentor in the technology you're using so anyone can get on board (those budding 10 year old computer geniuses make good additions to the engineering team).
5. Use state of the art data mining technology
6. Make WE project driven.
I hope this helps Bowo.
Sincerely,
Michael D. Alexander