In order to realize this vision, does every solution have to be implemented in PICK?
If the goal is to "make our development tasks more efficient" it is making sure the labor that one of us puts in is not reproduced by another, i.e. Pick syntax files for various tools. The "collaboration point" whether it is pickwiki or another, does not have to host the code, but pointers to the places where the resource can be maintained properly. An example is the MAKEXML program on the wiki. I have used that many times and I seriously appreciate ECL and KRJ for making it available. Is it perfect, not really, every time I use it, I get the docstring twice. The wiki is not the way to communicate that it needs a patch. If I did (which I should) fix my copy, who do I communicate it to? We also need to let people know under what license we post the code under. Can I put MAKEXML up on my github and patch it, giving attribution to ECL and KRJ? On Fri, Nov 18, 2011 at 12:04 PM, Wjhonson <[email protected]> wrote: > > As the OP, I like the idea of a wiki, provided it can either use straight > HTML, use MediaWiki markup (which is slightly different), or use a WYSIWIG > like sites.google.com or pbwiki uses. I find that only a few of these have > gained sufficient traction that most gearheads know how to use them, the > other competitors are just more headaches. > > Make it searchable. Sure. I assume that any web pages are searchable. You > have to actively make something not searchable AFAIK. > > Useful examples - hopefully. Make sense to everyone - probably not as > possible. But anything that doesn't make sense, you'd be able to markup > > I didn't address docs, but sure why not. > > Collaborate - that's the main point of my message really. To find a way to > collaborate that is more immediate, and more used that PickWiki which seems > very cob-webby to me. > > > > -----Original Message----- > From: John Thompson <[email protected]> > To: U2 Users List <[email protected]> > Sent: Fri, Nov 18, 2011 8:46 am > Subject: Re: [U2] Code Collaboration > > > So, I thought what the original poster was getting at was: > 1) Create a documentation/wiki/example site > ) Make it searchable > ) Have useful examples that make sense to everyone > ) Also post the vendor/var docs > ) Collaborate on ideas (like we do here) > Maybe you guys are talking about something else... > Github, svn, cvs, PRC and all those are great tools, but, they probably > ren't going to create the "Wikipedia" of the MV world. > The above can be done, but, it needs to become a living/breathing thing > hat gets updated a lot, otherwise, folks won't use it. Hence the > hallenge- making it a living/breathing thing. > I know this kind of thing has been tried, and is being tried... but there > robably isn't enough flag waving and marketing to keep it going. > Or people create something, and try to make it subscription based, which in > his day and time is never going to work with something like the above. > Some of the things I know about are: > http://www.nuwiki.com/cgi-bin/nuwiki.cgi?home&project=nuwiki > ttp://www.keyally.com/prdb/universe/basic_tree_all.html > ttp://www.pickwiki.com/cgi-bin/wiki.pl > Anyway, I'd like to help with something like that. I'm just not sure at my > tage in life, that I have the time to spearhead it and become the chief > Architect" of something like that. > > On Thu, Nov 17, 2011 at 6:05 PM, Wjhonson <[email protected]> wrote: >> > Personally I respond more immediately when something comes at me. > Would it not be possible to set up a mailing list for any changes to > Incubator code? So all users on that list get emailed when a change is > made? > I think this would propel both use of the code, and <s>misuse</s> > enhancement. > > > > -----Original Message----- > From: Brian Leach <[email protected]> > To: U2 Users List <[email protected]> > Sent: Thu, Nov 17, 2011 2:55 pm > Subject: Re: [U2] Code Collaboration > > > Mecki > Thats why the board launched the Incubator project early this year. The > intent > s for this to become a repository of useful working examples of using the > echnology. But I don't have the time to write those all myself and we have > been > rying to pursuade the community to get involved. > Brian > ent from my ASUS Eee Pad > Mecki Foerthmann <[email protected]> wrote: > >I think a major problem is the lack of training/documentation. > Great that there are all these new possibilities, but if you have to > figure everything out yourself it becomes very difficult to keep up with > the technology. > A lot of VARs (especially ours) are no help if you get the feeling they > know even less then you do. > It is very frustrating if the business asks, 'can we do that?' and you > can only answer, 'yes, I know it's possible but I don't know how to make > it work.' > And how am I to show the young guys all the flash things I have seen in > demos or heard about here if I can't get them to work myself? > > On 17/11/2011 20:55, David Jordan wrote: > > The U2UG board has been discussing with Rocket how to encourage > excitement > hat U2 is not legacy but is a technology leader. I was at a presentation > of a > 2 VAR and they demonstrated product that would be indistinguishable from > any > ther player in open systems, Service architecture, interoperability, web > ntefaces, etc. How do we get this across to the market. > > > > With collaboration, we need to first excite. How do we excite people > in U2 > echnology. Is it looking at a major enhancement of the BASIC programming > anguage or a new one within U2. What other things do we look at. > > > > Currently young programmers are excited by web technology's, mobile > apps, the > exy stuff. They are not interested in the backend, whether Oracle RDBMS, > SQL > erver or U2. This is a problem across the industry. > > > > The board of the user group are interested in areas to look at and how to > reate infrastructure to make this happen. If we can reignite excitement > in > he product and create a place for collaboration where that excitement can > be > ut to good use then I believe we can achieve success. However our success > epends on a group of people not a few individuals. If this is to occur, > it is > ime for people to become involved in shaping a future. > > > > Regards > > David Jordan > > VP U2UG > > _______________________________________________ > > U2-Users mailing list > > [email protected] > > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > ______________________________________________ > 2-Users mailing list > [email protected] > ttp://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > > > -- > ohn Thompson > ______________________________________________ > 2-Users mailing list > [email protected] > ttp://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
