tickets #126332
openFwd: How to add a new project under specific namespace?
0%
Description
Hi,
I've posted "How to add a new project under specific namespace?" [1]
Then Rubhan kindly advised me to contact admin@opensuse.org.
Here is the summary:
- want to create a completely new sub-project "milter-manager" under server:mail
- want me (kenhys) [2] as a maintainer role for that "milter-manager" sub-project.
[2] https://build.opensuse.org/project/show/home:kenhys
Could you create above one, please?
Regards,
---------- Forwarded message ---------
From: Rubhan Azeem rubhan.azeem@suse.com
Date: 2023年3月22日(水) 0:39
Subject: Re: How to add a new project under specific namespace?
To: Kentaro Hayashi kenhys@gmail.com
Hi Hayashi,
Thanks for contacting us. To create a new sub-project under
server:mail you need to contact the maintainers. They can create a
sub-project for you. If you want to create a completely new project
outside of your home project, you can send a request to
admin@opensuse.org.
I hope it answers your query. If that doesn't help then please let us know.
Kind regards,
Rubhan
From: Kentaro Hayashi kenhys@gmail.com
Sent: Monday, March 20, 2023 8:29 AM
To: buildservice@lists.opensuse.org buildservice@lists.opensuse.org
Subject: How to add a new project under specific namespace?
Hi,
According to https://build.opensuse.org/project/new,
When I want to create a new project outside of my home project,
I need to contact via email, but, apparently, it will not work because it
bounces email (noreply@opensuse.org). It seems that it is a known-issue since
2022.
[1] https://github.com/openSUSE/open-build-service/issues/12356
Is there documented instruction on how to request a new project under
existing specific namespace (such as server:mail) ?
What I learned from the existing documentation, it should create a
new project in my case, but I couldn't find official documentation to do it yet.
I've tried to use obs under my home project [2] whether it satisfies
our requirement
in beforehand.
Here are our requirements for milter-manager project:
maintain the package under the meaningful namespace
- package itself may be maintained under the home project, but it is better to maintain under a more meaningful namespace because milter-manager is related to mail service.
publish multiple versions in the same repository
- maintain the latest version only is not enough.
- It may work by submitting multiple versioned package to server:mail namespace, but it causes namespace polutions with milter-manager-1.x.x, milter-manager-2.x.x and more.
- To avoid such a situation, it should be server:mail:milter-manager project to group multiple versions under it's own project namespace.
want to publish not only openSUSE, but also other distributions
- It requires configuring project meta information to do, so it can't be satisfied with submitting packages to server:mail. It need to own server:mail:milter-manager project namespace.
To satisfy both of them, I want to create a new project.
Correct me if I understand wrongly.
Regards,
[2] https://build.opensuse.org/project/show/home:kenhys
--
Kentaro Hayashi kenhys@gmail.com
Updated by crameleon almost 2 years ago
- Category set to OBS
- Private changed from Yes to No
Updated by kenhys almost 2 years ago
Hi,
Is there any person to be assigned for helping with this ticket?
If there is missing information to do, I'll feedback.
Updated by dirkmueller almost 2 years ago
I can certainly create such a subproject for you, but before that I'm wondering what the goal is? server:mail is a devel project for openSUSE, and the home project you're mentioning is not actually building anything for a SUSE distro.
are you intending to use the open Build service as a location for an independent software delivery exercise? then a project below isv:
namespace might be most appropriate.
Updated by kenhys almost 2 years ago
are you intending to use the open Build service as a location for an independent software delivery exercise? then a project below isv: namespace might be most appropriate.
Thanks, as you mentioned, it seems isv:
namespace may be more appropriate.
Then, cloud you create isv:milter-manager
?
Updated by kenhys over 1 year ago
Hi, @dirkmueller, cloud you create isv:milter-manager
? (It is ok for empty project at the moment, I'll import content from home:kenhys manually)
Updated by darix over 1 year ago
my proposal would be server:mail:milter-manager to keep it in the scope where the other mail related packages can be found.
Updated by kenhys over 1 year ago
darix wrote:
my proposal would be server:mail:milter-manager to keep it in the scope where the other mail related packages can be found.
Hi, @darix
Currently, openSUSE is not supported yet, isv:milter-manager is an appropriate namespace.
Updated by dirkmueller over 1 year ago
kenhys wrote:
Currently, openSUSE is not supported yet, isv:milter-manager is an appropriate namespace.
darix pointed out earlier to me that isv:
is reserved for the original upstream author of the project, which I think you are not (correct me if I'm wrong on that).
in that sense, 'server:mail:milter-manager' appears to be a good tradeoff (it isn't the exact devel project).
Updated by dirkmueller over 1 year ago
project created and assigned ownership to you.
Updated by dirkmueller over 1 year ago
(don't have permission to close the ticket, somebody else needs to do that)
Updated by kenhys over 1 year ago
Hi, @dirkmueller
darix pointed out earlier to me that isv: is reserved for the original upstream author of the project, which I think you are not (correct me if I'm wrong on that).
isv:milter-manager is appropriate because I'm a member of upstream authors. (kou and me - kenhys)
https://github.com/milter-manager/milter-manager/graphs/contributors
Could you reopen this issue (and create isv:milter-manager instead)? (I don't have permission to do so)
Updated by smithfarm 6 months ago
- Status changed from New to Feedback
So, a year has passed.
Do you still need a isv:milter-manager project created in OBS?
What should we do with https://build.opensuse.org/project/show/server:mail:milter-manager which has already been created, but is apparently not used?