7. For changes in the website should be the standard process we already use: all committers can approve the changes. The content should be approved gradually by people who are most familiar with the project.
On Fri, Nov 29, 2019 at 6:49 AM Jarek Potiuk <jarek.pot...@polidea.com> wrote: > Thanks Kamil for the overview of the current state of the process. I > approved it, but I'd love others take a look as well if there is no problem > with this small-ish +2,473,672 changes PR ;). Kinda nice review for a > weekend ;). > > I think it is important that we at least briefly discuss this: > > > > 7) How do we approve code there? Do we use standard process as we do for > commits? > > > > Happy reviewing everyone, > > J. > > On Fri, Nov 29, 2019 at 3:36 PM Kamil Breguła <kamil.breg...@polidea.com> > wrote: > > > Hello community. > > > > We have a new website. The development phase is over, but the maintenance > > phase begins. > > http://airflow.apache.org/ > > > > I would like to give you some technical and organizational information: > > > > 1. We have three branches: > > * asf-site - contains generated files e.g. HTML; > > * master - empty, but I would like the source code of the website to > appear > > here; > > * aip-11 - source code e.g. templates, text content, documentation > archive, > > sphinx theme for generating documentation. > > I would be happy if PMC accepted PR to move the code from the aip-11 > > branch to the master branch > > https://github.com/apache/airflow-site/pull/174 > > In the next step I will set up a Jira ticket to set the main branch to > > master. > > 2. The website is not yet configured CD due to waiting for GitLab CI. I > > would like to be a manual CD until this problem is resolved. The problem > is > > mainly due to concerns about security and write access to the repository. > > More information about GitLab CI: > > > > > https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-23+Migrate+out+of+Travis+CI > > 3. Some other minor feature requests and suggestions are available in the > > Aizhamal's document: > > > > > https://docs.google.com/document/d/1YIgz0vZiw7zJsLzCiPun6n1VqPH1OuZGaSA_7EBixT8/edit#heading=h.pc0zvx280sy2 > > I will soon transfer them to Github Issues > > 4. We have guides that describe how to make changes to the project. > > > > > https://github.com/apache/airflow-site/blob/e601af1e7d121038e461d16cb7376086196e9059/README.md > > > > > https://github.com/apache/airflow-site/blob/e601af1e7d121038e461d16cb7376086196e9059/CONTRIBUTE.md > > > > > https://github.com/apache/airflow-site/blob/e601af1e7d121038e461d16cb7376086196e9059/sphinx_airflow_theme/README.md > > 5. We still lack content for the website. A document that enables > > discussions on text content: > > > > > https://docs.google.com/document/d/1Y4jBjtQ13zeLZ2e3V4foa51pN-168p1DHJ5zc7cbyGg/edit# > > 6. The website will appear in the portfolio of Utlio - > > https://utilodesign.com/ (daughter company of Polidea). The team is open > > to > > ongoing discussion in the community about proposals for improving the > > appearance. Some people love their projects like children and do not want > > them to get hurt. If you want to create a website for your company, > please > > contact me - kamil.breg...@polidea.com. > > 7. There is one more open question about maintaining process. Do we want > to > > establish one person who will accept the content and control its quality? > > Do you have another idea about editing content? > > > > If you have another question about the website, I will gladly answer. > > > > Best regards, > > Kamil Breguła > > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48%20660%20796%20129> <+48660796129 > <+48%20660%20796%20129>> > [image: Polidea] <https://www.polidea.com/> >