Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Update contrib guide: working on Flux issues #2104

Merged
merged 9 commits into from
May 29, 2019
Merged

Update contrib guide: working on Flux issues #2104

merged 9 commits into from
May 29, 2019

Conversation

dholbach
Copy link
Member

  • fix some markdownlint things
  • add section about working on Flux issues
  • refer to calendar invite for Flux meeting

Daniel Holbach added 3 commits May 28, 2019 17:34
Signed-off-by: Daniel Holbach <[email protected]>
Signed-off-by: Daniel Holbach <[email protected]>
@dholbach dholbach added the docs Issue or PR relates to documentation label May 28, 2019
@dholbach dholbach self-assigned this May 28, 2019
* [Committing a small change](#committing-a-small-change)
* [Confirm the change landed](#confirm-the-change-landed)
* [Conclusion](#conclusion)
- [Prerequisites](#prerequisites)
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it was https://github.com/DavidAnson/markdownlint/blob/v0.11.0/doc/Rules.md#md004---unordered-list-style that showed up for me. I can roll back the change too.

Copy link
Member

Choose a reason for hiding this comment

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

I think that is because the default configuration is not set to 'sublist' style.

For example, the following is valid for the sublist style because the outer-most indent uses asterisk, the middle indent uses plus, and the inner-most indent uses dash:

* Item 1
  + Item 2
    - Item 3
  + Item 4
* Item 4
  + Item 5

I have no strong opinion on this but I think it improves readability for raw markdown files (which I read more often than parsed files).

CONTRIBUTING.md Outdated

## Working on issues

If you like Flux and want to get involved in the team, a great way to get started
Copy link
Member

Choose a reason for hiding this comment

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

Some people may take "team" to imply something more formal than what's meant here. To avoid introducing this ambiguity, you could omit the mention here and in the next para. (It would be good to retain the welcoming message at the end, if it can be done)

Copy link
Member

@squaremo squaremo left a comment

Choose a reason for hiding this comment

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

More language finickiness

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated
The idea here is that new issues are first confirmed by somebody in the team,
which might require asking for more information, testing with a fresh Flux
environment and once confirmed (and more information added to the issue), removing
the `blocked-needs-validation` label. Afterwards the issue can be worked on and
Copy link
Member

Choose a reason for hiding this comment

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

.. a fresh Flux environment. Once confirmed, the blocked-needs-validation label is removed, and the issue can be worked on ...

Daniel Holbach and others added 3 commits May 28, 2019 18:30
Copy link
Member

@squaremo squaremo left a comment

Choose a reason for hiding this comment

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

Text is good -- thanks Daniel 🍱
(Is there a markdown thing to resolve?)

Signed-off-by: Daniel Holbach <[email protected]>
@dholbach
Copy link
Member Author

Screenshot from 2019-05-29 07-27-02

Everything done now, apart from the sublist changes in Markdown.

@dholbach
Copy link
Member Author

🏁 🏎️

@dholbach dholbach merged commit 91acc07 into fluxcd:master May 29, 2019
@dholbach dholbach deleted the update-contrib-guide branch May 29, 2019 06:56
@hiddeco hiddeco added this to the v1.13.0 milestone May 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
docs Issue or PR relates to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants