I already had a talk with people at Microchip India. I was invited to attend Microchip Masters in India to collect an ipad Mini from their COO as I won their Core Independent Peripheral Contest. I had a presentation to make regarding a new platform which I call UPPA Universal Programmable Product Adapter currently based on PIC and JAL.
The problem was I didn't have a clear answer on what we need from Microchip for JAL. Same happened for my presentation where I had working prototypes but I did not get a chance for a formal presentation. Also among the 4 people to whom I introduced the concept only one was not convinced but he was the decision maker. Coming back to the original point raised by Rob, 1. It has been (too) quiet here lately, especially on the development side! Some people have withdrawn from the Jallib team for whatever reason and we have to respect that: nobody is paid for his contribution(s) so we cannot put any claim on them! May be its just that people don't have enough time, Yes there might be time limitations, there might also be situations where you hit the wall with JAL where you are forced to use C or languages. Like USB not usable for 16f1455 . 2. There were only few new contributions last year and hardly anybody did any maintenance on the existing libraries or solved any of the listed issues. But the variety of PICs has grown! We are not able to create enough buzz to have enough JAL users to great published JAL projects. 3. It is unrealistic to assume that the remaining people will take over all the 'open' tasks! On the contrary: I'm afraid these people will quit because it becomes too much for them. I don't think anybody will take up Rob's or Kyle's job unless there's a killing reason and incentive. I'm afraid that with this trend Jallib will die pretty soon! That would be a waste of time and effort of all those who contributed to Jallib. I think it is due time that some of you (who profitted of Jallib) fulfill some of vacancies. 1) JAL will remain in the hobby mode where people might use it but not talk about it enough unless there's a killer buzz creating app. 2) Discussions on jallist or google groups does not have the effect of a forum on the web, even though jallib pops up in any search on 8 bit PIC micros, I feel people would go into more details and jal website would come up higher in search results if the forum is integrated and part of the current jal web site. 3) One of the great benefits of JAL is that we have so many separate samples for most functions and for all PICs. Matts SD card library helped recently, We got to promote it through website. 4) JALlib should not limit accepting libraries or samples based on cosmetic issues like case sensitivity of variable names. Just a continuation to some random thoughts of Rob.. Sunish On Fri, Feb 21, 2014 at 11:46 AM, Oliver Seitz <[email protected]> wrote: > That's true. We could however ask Microchip for sponsoring. > > If that fails, physical presence is not needed for some kinds of assistance. > Leaflets or posters can be designed, demo boards can be built and the like. > For a circuit board, the jorney is affordable. For digital data, very much > so :-) (And I have access to a colour A3 printer) > > And then, there are people from europe involved at jallib, too ;-) > > Anyway, I appreciate your moral backup :-) > > Greets, > Kiste > > ________________________________ > Von: mattschinkel <[email protected]> > > > I am interested, but I don't live across the street so it would be costly to > get there. > > Matt. > > On Wednesday, February 19, 2014 1:49:43 AM UTC-5, Kiste wrote: > > "Having a complete package is a good thing." > > This is true. But the world is not static. There is 16-bit PWM now. There is > 8-bit DAC. There is floating-point math. Neither of which is supportet by > jallib, IMO. > > Advertising by posting projects in the web is a way, and an easy one. It is > one, however, which many people go. I'd like to repeat the proposal I've > made before: Soon is the time to apply for a gratis open-source-project > booth at http://www.linuxtag.org/2014/ en/ . > > If someone is going to help a little in any way, I'm prepared to put quite > some effort in such a project. I'm familiar with trade fairs and I can reach > the location by subway. > > I even have some hundred old PCBs as giveaways, which can be used for MAX232 > level converters. I can laser-cut the jallib URL onto those PCBs. > > I have touch sensors and a LED-tile with 40 RGB-LEDs as exhibits. > > Is anyone even a little interested? > > ________________________________ > Von: mattschinkel <[email protected]> > An: [email protected] > Gesendet: 2:19 Mittwoch, 19.Februar 2014 > Betreff: [jallib] Re: jallib team > > Hi Rob, > The team has done a great job with the package we have created. It seems > that Jallib is mostly complete, which causes less commits. Having a complete > package is a good thing. > I and others just don't have time lately, although I do plan to get back > into it and write more tutorials and put more work into bits of my current > libs. When I was writing the tutorials and posting about them on Jallist and > elsewhere, it was good advertising. This seemed to produce new interest. > You are a huge contributor at the moment. We all greatly appreciate the work > you put into the device files. I'm not sure how to word this, but if you > look at the amount of work you are putting in, and compare it to the number > of other committers/users, it seems like you are doing too much for the > "worth" of the additional device files. I think the answer is no, but is > there any way to automate your device file creation? It may be more > efficient to put your work in elsewhere. You could also choose to only > update device files once per year, or whenever there is a need to do so do > too a request. I don't think people use these new device files much. > I think we need to think up new projects and idea's, and you could assist > better here. Maybe start a large project as a group and try to build > something crazy that can get attention. > Some examples of things that could help, please add. > 1. Help Kyle with the compiler to get new devices to work with it to get > interest in the language. > 2. Help Kyle with the compiler to make Jalv2 a cool scripting language for > linux/windows. will need a new set of libs, and therefore more commits. > 3. Work on whatever lib needs the most work. I'd say that would be the GLCD > libs. Do a complete rewrite? > 4. Start a project.. Send Jallib to space? Start an AI project? Build a > robot? > 5. Publish a book > > Matt. > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jallib+un...@ googlegroups.com. > To post to this group, send email to [email protected]. > > Visit this group at http://groups.google.com/ group/jallib. > For more options, visit https://groups.google.com/ groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jallib. For more options, visit https://groups.google.com/groups/opt_out.
