Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#2053 - Update Contributing Document #2113

Merged
merged 4 commits into from
Jun 14, 2018
Merged

#2053 - Update Contributing Document #2113

merged 4 commits into from
Jun 14, 2018

Conversation

ohine
Copy link
Contributor

@ohine ohine commented Jun 12, 2018

Summary

This updates our contributing guide to point people to the current issue tracker (it was still linked to jira). I also added commands required to get git setup for the first time and to help other users rebase their forks to the current code base.

If @dnnsoftware/tag has any other suggestions, lets hear them so we can help everyone participate together!

Fixes #2053

@ohine ohine modified the milestone: 9.2.1 Jun 12, 2018
Copy link
Contributor

@mitchelsellers mitchelsellers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes to this look good!

@ohine ohine added the Community Legacy label used to identify community contributions label Jun 12, 2018
@@ -60,12 +61,6 @@ appropriate to start the first line of a commit with '(doc)' instead of
a ticket number.

````
(doc) Add documentation commit example to CONTRIBUTING
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why were the first lines of the example commit messages removed? I think these either need to be complete examples (as they previously were) or they need to be removed altogether and replaced with a link to documentation on writing a good commit message.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seemed like boilerplate text which didn't make sense to me. If it does make sense to keep, I'll add it back. L31-L38 and L63-L68 are the blocks I'm referencing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a little confusing, but it's supposed to be an example commit message (for a commit about adding the commit message example, which is probably why it gets confusing). Maybe using a more concrete example would be better.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is the latest update?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect

@valadas
Copy link
Contributor

valadas commented Jun 12, 2018

I like it, but it would also be nice to show how to build from sources, if people only get this repo, they are not getting a working Dnn, so how should this be done, is there a way to get this + persona bar + pb module, etc. into a single location, build from github sources and then have all that in visual studio to edit, build test.

Or do people just get the zipped sources from Dnn Nightly buil and then move over the change into the VS Project cloned from here?

@bdukes
Copy link
Contributor

bdukes commented Jun 12, 2018

Agreed, @valadas. We're working on getting the build and packaging more streamlined, but until then, there should probably be a note to start with a package from the nightly feed (is this still being updated, with the changes being made to the CI?).

Once we have the packaging of the various components coming together, we can hopefully update to a much simpler process.

@mitchelsellers mitchelsellers merged commit 66159d2 into dnnsoftware:development Jun 14, 2018
@ohine ohine added this to the 9.2.1 milestone Jun 21, 2018
@ohine ohine added Community Legacy label used to identify community contributions and removed Community Legacy label used to identify community contributions labels Oct 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Legacy label used to identify community contributions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants