konveyor / community Goto Github PK

@jameslabocki We had hosted Move2Kube website in konveyor.io/move2kube from https://github.com/konveyor/move2kube/tree/gh-pages. But after the new webpage refresh the link seems to be broken.

Is konveyor.io no longer hosted in github.io? If so, what is the right way to bring back the project pages?

Description

Hi All,

I would like to propose adding Dylan (@dymurray ) to the list of Maintainers. Dylan has been an active contributor of the Konveyor community. He has been leading multiple efforts like Konveyor planning, triage, end user interactions, and many more. He would be a great addition to the leadership.

Inviting the steering committee members to vote in this issue with a +1 (yes) or -1 (no) registering their choice - @jwmatthews @tsanders-rh @rromannissen @JonathanR19 @tamintheclouds

Please feel free to reach out if you have any questions.

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

n/a

Description

Konveyor AI (Kai) is Konveyor's approach to easing the modernization of application source code to a new target by leveraging LLMs with guidance from static code analysis, augmented with data in Konveyor that helps to learn how an organization solved a similar problem in the past. Kai is now in full-fledged development, with a minimal viable demo already available. We would like to move it to the Konveyor organization to better integrate with the Konveyor hub and create future release artifacts.

Deep Dive Konveyor AI: Konveyor AI Deep Dive - 2024

This issue will remain open until we achieve a steering majority, which is 2/3 (5 votes). Please show your support by adding +1 to this issue. If you have any comments, please add them to this issue or reach out to the maintainers.

Additional Information

No response

Votes

• Dylan Murray
• Todd Sanders
• John Matthews
• Ramon Roman Nissen
• Jonathan Recinos
• Tam Nguyen
• Savitha Raghunathan

@djzager @jmontleon Adding it here for tracking purposes. Once we have an automated release process, would you both be able to help with documenting the release steps?

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

No response

Description

Create a mechanism to provide contributor badges that folks contributing to the project and that way they can showcase their contributions.

Additional Information

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

No response

Description

No response

Additional Information

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

0.2

Priority

Critical

Current Behavior

No response

Expected Behavior

No response

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

/assign

Create a digest for Konveyor project and send it out to community, preferably the start of every quarter

1. code of conduct
2. Steering
3. maintainers + leads

In https://github.com/konveyor/community/blob/main/MAINTAINERS.md, there is the requirement that each repository have a OWNERS.md file. I think there are 2 problems there:

• OWNERS file, despite not having extension, is YAML format, so I think it should not be markdown (md extension). Ref: https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md
• OWNERS file are usually used for CI, but it seems they are being used just for information. Could this information be passed in another way?

If this should really be a requirement, maybe creating a job in https://github.com/konveyor/release-tools would be the best way to enforce this rule.

Related to konveyor/release-tools#53

Filing here because there doesn't seem to be a repo for the website? (where is the website content?)

Currently, the website has no information on how to join the various mailing lists, attend community meetings, or anything else. This would be the same information that's present here It only has a "contact us" form. This is a bad approach; new community members will prefer to opt-in, rather than signing up for spam.

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

No response

Description

As part of our ongoing effort to ensure all the websites within the CNCF meet the CLOMonitor guidelines, we noticed that Konveyor does not pass the website criteria on CLOMonitor.

To fix this:
Edit konveyor/community repository details

In the website section, add the link to the Konveyor website. See Notary for example:

Once done, feel free to close this issue as CLOMonitor will recrawl the page and update accordingly.

Additional Information

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

0.3.0-alpha.5

Priority

Critical

Current Behavior

test

Expected Behavior

test

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

0.2

Priority

Undefined (Default)

Current Behavior

No response

Expected Behavior

No response

How Reproducible

Never

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

Please update the konveyor website to have https://github.com/konveyor/tackle as the tackle entrypoint in GitHub projects.

konveyor/enhancements#160 talks about enforcing standards for what it means for an issue (and maybe later) a PR to be triaged. However, we don't currently have a document that details these so called standards.

Create an issue_triage.md that explains:

1. Triaged issues will have a triage/accepted, kind/*, priority/* label. If they don't they will be marked with needs-(triage|kind|priority).
2. If an issue is an issue suitable for new contributors, we should label it good first issue.
3. ... maybe more.

This might be a good reference for ideas on what all might be included in the document...but we aren't really trying to mirror Kube. https://www.kubernetes.dev/docs/guide/issue-triage/#triage-related-tools

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

NA

Description

Add automation around /assign comment that can assist with self-assigning issues.

Additional Information

No response

Remove Forklift project reference
update meeting details

Currently, each repo when it gets released, they have changelog/release notes associated with it. Going forward we would like to find a way to consolidate this and publish it in community repo whenever we have an operator release.

https://github.com/cncf/foundation/blob/main/project-maintainers.csv should have konveyor maintainers listed

Should the content of this file https://github.com/konveyor/release-tools/blob/main/VERSIONING.md be in https://github.com/konveyor/community/blob/main/CONTRIBUTING.md? This would be better for developers, as all information would be consolidated in a single file.

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

n/a

Description

The Konveyor project would like to develop documentation showing users how to leverage Konveyor for solving a wide number of use-cases.

One of the issues we see in the community is that new adopters may not realize the potential of how/where they can leverage Konveyor. We intend to help with this problem by building a number of guided scenarios, documentation with examples that a user may run through such as a 'getting started guide' tailored to specific use-cases.

This specific issue is for us to track how we can do the work on the Maintainer side to arm new contributors to help us with this documentation effort.

The rough idea is that as maintainers we will:

• Choose a few use-cases we believe will be of interest to adopters
• Create a tracking issue and a getting-started doc for each use-case to guide a new contributor, and label with 'good first issue'
• Provide assistance to the new contributor for questions as they work through learning Konveyor and use Konveyor to solve that use-case
• Provide assistance to the new contributor for blog post creation, perhaps jointly collaborating on the writing together with a Konveyor developer
• Help with publishing the documentation in our docs site, and/or publishing a blog post if applicable

For each target scenario we are imagining:

• Tracking issue, so a new contributor may ask questions and be assigned, or sub-issues may be broken out and tracked so multiple contributors may work together
• A Konveyor community member will own creation of a getting-started document that captures background knowledge of the problem domain, links to technologies involved, recommend sample application characteristics, analysis rules needed, etc
• In addition the Konveyor community member will create an outline of what they imagine the scenario should entail when it is written up.
• A Konveyor community member will volunteer as a sponsor for this work and as such will help to mentor a new contributor to pickup this issue and work.

The intent is to create enough guide rails for the new contributor so they have a clear path of:

• Understand what technologies to learn to achieve the scenario
• Understand what pieces of Konveyor to leverage and how to accomplish the scenario
• Have a rough idea of what is expected in the scenario so they have guidance of how to document this scenario
• Know how to contact other community members in Konveyor to ask for guidance and help with learning more

We are considering this work to be a great way for new contributors to dive into Konveyor and learn an area by gaining real-world exposure to solving an end user need. As they learn the specific area of interest and gain user empathy, the will share their learnings via documentation to aid other users to ramp up quickly in using Konveyor....with this knowledge the contributor gains, they will set themselves up to dive deeper into interest areas for code contributions. (The thought is this helps to solve one of the more challenging aspects of how to contribute in a new domain without understanding how the solution is used by an end user.)

Additional Information

No response

All: If anyone want in/off of the task items, let me know.

To recognize contributors, lets add a section to the release page mentioning their name and PRs. For example - https://github.com/openshift/oadp-operator/releases/tag/v1.1.0

@djzager @jmontleon is this something that can be added to the automation?

cc: @pranavgaikwad @jwmatthews

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

No response

Description

No response

Additional Information

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

0.2

Priority

Undefined (Default)

Current Behavior

No response

Expected Behavior

No response

How Reproducible

Never

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

NA

Description

template to file feature requests

Additional Information

No response

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

NA

Description

• Improve Bug template with details
  for example if someone is using the latest commit from main branch then what should be the Konveyor version ( commit id may be? )

• Look for improvements and make it easier to file bugs ( look into the fields and make a few optional)

Additional Information

No response

As part of the continuing work to refocus Konveyor on the Modernization use-case we have decided to rehome Pelorus to a new org dedicated to the development of Pelorus: https://github.com/dora-metrics/pelorus

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

No response

Description

Planning to kickstart a contributor spotlight series to share Contributor's experience with wider audience as well learn from their experience. Idea is that it will be an interview style format with questions and answers, published at a regular cadence.

Areas:

• Testing
• UX
• CI
• Product manager
• LFX mentee
• End user
• Contributor
• Maintainer
• and More.....

Additional Information

No response

https://kubernetes.slack.com/archives/C04QZJFQ0UA/p1678979138332489?thread_ts=1678970730.528859&cid=C04QZJFQ0UA