I would follow this approximate process: 1. Google to see if you can find information on the feature you want - to see if perhaps it is already implemented or if there is already an RFE for it. 2. Post a question on Stack overflow or the mailing list to ask how to achieve what you want. 3. If, after asking, it is clear that the feature hasn't been implemented already, then file an issue in the issue tracker. 4. If you are interested in implementing the feature yourself, mention that in the issue. Ask for help there too, if you need some direction on where to start.
5. If you do decide to implement it yourself: 5a. Fork the relevant repository 5b. Create a branch specifically for the feature you're working on. 5c. After you have implemented the feature, make a pull request, referencing the original issue in the issue tracker. 5d. Link to a minimal test case that allows others to test your changes. For bonus marks, create unit tests. Any contribution is appreciated. The simpler you make it for us to incorporate your contributions, the more likely it is to be merged in a timely fashion. On Mon, Aug 27, 2018 at 2:30 PM, <[email protected]> wrote: > ok, and what is the way to ask for some functionality? > > > On Monday, August 27, 2018 at 12:34:06 PM UTC-3, Steve Hannah wrote: >> >> >>> Personally, I tryed to solve those problems two years a go , even I pull >>> a request. If you remember time a go, somebody ask to upgrade the google’s >>> api version to 9.4.0 do you remember? Because it take a lot of time I gave >>> up and I decided to quit my development canceling my suscripción. >>> >> That was added about a year ago. >> https://github.com/codenameone/codenameone-google-maps/ >> commit/1bbe0154be21831b95abaff14b5c2b8e604fa5bf >> >>> >>> >>> If the right option is the second , I asked to my self :”why if we use >>> this tool to simplify our projects, why we don’t contribute to make it more >>> robust?? >>> >> >> Even for community contributions, the best way to start is with an RFE -- >> unless it is a very trivial pull request like javadocs, or fixing typos. >> That way, when we get the pull request, it is clear what it is solving. It >> also gives everyone a change to provide feedback before someone spends a >> lot of time working these new features. >> >> >> >> -- > You received this message because you are subscribed to the Google Groups > "CodenameOne Discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/ > group/codenameone-discussions. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/codenameone-discussions/4b3747bc-4d86-4de3-8658- > af0a95088171%40googlegroups.com > <https://groups.google.com/d/msgid/codenameone-discussions/4b3747bc-4d86-4de3-8658-af0a95088171%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Steve Hannah Software Developer Codename One http://www.codenameone.com -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKW%2B33XH6FKS90M3ePG7gCgemB8P5L%3DeVvUO2-7RXbT4nQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
