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

few items for TSC meeting agenda #176

Merged
merged 2 commits into from
Jul 1, 2024
Merged

Conversation

arhimede
Copy link
Contributor

@arhimede arhimede commented Jun 2, 2024

I am still checking , maybe there are items to be added or expanded

Q A
Documentation yes/no
Bugfix yes/no
BC Break yes/no
New Feature yes/no
RFC yes/no
QA yes/no

Description

I am still checking , maybe there are items f=to be added or expanded

Signed-off-by: arhimede <julian@dotkernel.com>
Comment on lines +38 to +45
### OSS status for packages

For each package, add a file OSSMETADATA , with possible values
- osslifecycle=active
- osslifecycle=maintenance
- osslifecycle=archived
and add the badge to readme file
Example: ![OSS Lifecycle](https://img.shields.io/osslifecycle/dotkernel/api)
Copy link
Contributor

Choose a reason for hiding this comment

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

This would really benefit to also have the date when the status was last reviewed.

Some packages might have very few recent code changes by design (so looking dead-ish). But showing that it was recently re-confirmed as "active", would clear up all possible confusion. On the other hand a package might be so dead and forgotten that we didn't even remember to update its status to "archived". So at least showing that the status was last review was 5+ years ago, would let us know that something is wrong.

Comment on lines +28 to +36
### getlaminas.org website update

We need approval for :
- https://github.com/laminas/getlaminas.org/issues/162
- https://github.com/orgs/laminas/projects/23/views/1

Dotkernel organisation want to be involved in this, with Frank Brückner @froschdesign as project lead.

The purpose is to have it ready on a new staging location , by July TSC meeting, for final approval .
Copy link
Member

Choose a reason for hiding this comment

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

Every pull request is welcome. Ideas can also be suggested in the chat.

Comment on lines +12 to +20
### Create Media Kit

- create new logos or improve the current ones , for Laminas and Mezzio
- svg format, various sizes and color
- create few wallpapers
- stickers from stickermule
- banners and badges: "powered by Laminas " , or "powered by Mezzio"
- official banner/seal for "Official Laminas Commercial Vendor"
- any other ideas related to marketing materials
Copy link
Member

@froschdesign froschdesign Jun 19, 2024

Choose a reason for hiding this comment

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

I would postpone this because, firstly, I don't see an urgent need and, secondly, there are other tasks that are of greater importance and visibility - like the website itself.
(The logos in SVG format can be found in the website repository.)

Comment on lines +51 to +56
### Create a status page
[See this pull request](https://github.com/laminas/technical-steering-committee/pull/175)

For each Github namespaces: laminas-api-tools, laminas, mezzio, and for each package in the namespace:

List all packages and the badge for each , with its OSS status : active, maintenance, archived
Copy link
Member

Choose a reason for hiding this comment

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

This has already been discussed in the past. Some updates can be found in #175.

Signed-off-by: Matthew Weier O'Phinney <matthew@weierophinney.net>
@weierophinney weierophinney merged commit b8938df into laminas:main Jul 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants