I have gone through the process (code fork, JIRA account, etc.) to contribute to spring-related projects from GitHub.
But I am not sure how to assign a JIRA issue to myself because I don't see any such option on the JIRA instance.
Can someone please guide me as I would like to start contributing?
Contributing to a spring-related issue is quite easy. For the spring framework there is a contributing page on the github repository.
Other spring-related projects have a similar setup so check the project you are interested in for more information.
As for assigning issues, it is reserved to the team as every pull request (patch) is first reviewed before being applied. If you are willing to work on an issue, just say so by adding a comment and we'll assist you.
Related
I am a developer from who wants to create an ecosystem around micro services. My research led to your software projects, which are outstanding in many respects.
Unfortunately, one of the components I couldn't get running for an initial review was the portal.
The build failed due to a missing light-4j version (1.5.29).
The light-4j master branch is at 1.5.23, hence I checked out the portal at a version that meets the light-4j version. With this the docker-compose-hybrid.yml script failed, due to other missing libraries. Considering the fact that I even reverted to an older version of the portal sources, I am almost sure that I am on the wrong track.
Do you have any advice for me how to get this solved?
Thank you in advance.
Thanks a lot for your interest in the light platform. The light-portal is still in heavy development in develop branch which is depending on the develop branch of light-4 and other libraries. The easiest way to build it is through light-bot which is our own DevOps tool for microservices as you can see you are dealing with too many dependencies and most DevOps tools on the market can only deal with one repository each time.
https://github.com/networknt/light-config-test/tree/master/light-bot/develop-build/build-portal
Also, please be aware that light-portal services are built on top of light-hybrid which is a serverless framework. The build process just creates small jar files and copy to the read and write service folders. You need to start a compose to start the two services to load all the services.
The following the docker-compose to start the light-portal locally.
https://github.com/networknt/light-config-test/tree/master/light-portal
I am starting to write a light-portal tutorial but there are still a lot of topics are missing. Please let me know if you see any gaps so that I can add more info into it.
https://doc.networknt.com/tutorial/portal/
The mail might not be the best channel as the communication is on a private channel. In the future, you can ask questions on gitter as other people might know the answer when our team members are not available immediately. Also, the answers on the public channel might help other users to learn the platform.
https://gitter.im/networknt/light-4j
We have recently migrated to jira agile and the issues have changed from tasks bugs to stories. We have been using maven changes plugin to automatically send notification for new releases and it successfully includes issues resolved and so on. Now that we have stories, it does not include them to the message body. I have updated the configuration properties to include stories also and all possible issue types (Bug, New Feature, Task, Improvement, Sub-task,Story) but still no success. The jira report that is generated by the same plugin is correct but the mail still does not include them.
I also tried to attach the jira report (${basedir}/target/site/jira-report.html) but with no success.
Can anyone propose a solution or a work around too this issue?
After some further research and a lot of code checking in the source code of maven changes plug-in I found out that you have to include the following mapping in your configuration
<issueTypes>
<add>Story</add>
<fix>Bug</fix>
<update>Task</update>
</issueTypes>
This will inform the maven changes plug-in to map the build in xsd add,fix,update to Story, Bug, Task issues that are created with agile jira
I am developing a Java framework/API to solve a problem at a client. The code/idea is my property (not the client's). I think it might be useful for others, so I would like to publish it as a open source project.
By publishing I mean bringing it out in the open - making it available as a Maven project.
I can think of conforming to Maven structure, proper documentation/example usage available on a web site, and unit tests, maybe some code coverage threshold.
But does it have to be run by some committee? Do I have to present it to somebody? What steps do I need to take to eventually have it available as a Maven dependency?
There's no committee or approval process that I know of. All you have to do is put your code into a public Github repo. This is how open source software works.
Per Kapep's excellent suggestion below, you have to choose a license as well. Apache, Creative Commons, Gnu, MIT - these are a few of your choices. Know what they mean before you decide.
Your problem begins on that day - you'll have to make others aware of it and see if it's adopted by others. If it's good, you'll have the nice problems of dealing with a user base and having others change your code. If not, it'll languish in the repo.
I am not finding the drafts for Protocol and Study profiles or resources. I had found them in the past, but i dont remember where. We want to make a prototype for trials and continuity of care with patients at home.
I appreciate any link .
Thanks in advance
Regards
The very latest version is here: http://hl7-fhir.github.io/. This is the continuous integration build based on the version control. As for now, neither the Protocol nor Study resources have been added to the version control, though they have been proposed in concept.
Does anyone have any information on Spring Web Flow 3 status?
Here are a few relevant links that support my sense that springsource has essentially abandoned the project:
1)Official roadmap indicates they are missing milestones by over a year now with no update to the roadmap.
2)Forum thread filled with these questions ignored by Keith Donald and Spring team.
3)Official Download page says the latest release is 2.2.1 but is actually 2.3 so that is not even being kept up-to-date anymore.
While Web Flow version 2 I'm sure is a great product, the issues above are all obvious red flags when it comes to evaluating an open source product -- as well as evaluating the company behind that project. Am I simply missing some communication channel where all this has been discussed in detail before? I find it hard to believe that springsource, a company that seemingly had their act together, would be this negligent with one of their flagship products.
They just added a graphical web flow editor into STS. See this InfoQ post. Also, I just checked JIRA and Fisheye and it looks like there's bug fixes going into a 2.3.1 coming that corresponds with Spring 3.1. So I don't think it's abandoned, it's just not getting new features.
Just wanted to mention that the latest version (2.3.1) of Spring Web Flow was released on Mar 27, 2012. See the changelog file: http://static.springsource.org/spring-webflow/docs/2.3.x/changelog.txt