konveyor / community Goto Github PK
View Code? Open in Web Editor NEWDocumentation for Konveyor Community
Home Page: https://konveyor.io
License: Apache License 2.0
Documentation for Konveyor Community
Home Page: https://konveyor.io
License: Apache License 2.0
@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?
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.
n/a
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.
No response
Votes
@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?
No response
Create a mechanism to provide contributor badges that folks contributing to the project and that way they can showcase their contributions.
No response
No response
No response
No response
0.2
Critical
No response
No response
Always (Default)
No response
- OS:
No response
/assign
Create a digest for Konveyor project and send it out to community, preferably the start of every quarter
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.mdOWNERS
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.
No response
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.
No response
0.3.0-alpha.5
Critical
test
test
Always (Default)
No response
- OS:
No response
0.2
Undefined (Default)
No response
No response
Never
No response
- OS:
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:
triage/accepted
, kind/*
, priority/*
label. If they don't they will be marked with needs-(triage|kind|priority)
.good first issue
.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
NA
Add automation around /assign
comment that can assist with self-assigning issues.
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.
n/a
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:
For each target scenario we are imagining:
The intent is to create enough guide rails for the new contributor so they have a clear path of:
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.)
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?
No response
No response
No response
0.2
Undefined (Default)
No response
No response
Never
No response
- OS:
No response
NA
template to file feature requests
No response
NA
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)
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
No response
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:
No response
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.