Re: Question on adding new contributors

2017-06-05 Thread Dusty Mabe 


On 06/05/2017 05:25 PM, Josh Boyer wrote:
> On Mon, Jun 5, 2017 at 4:55 PM, Dusty Mabe  wrote:
>>
>>
>> On 06/05/2017 04:48 PM, Josh Boyer wrote:
>>> Hi Atomic group,
>>>
>>> The Atomic PRD (https://fedoraproject.org/wiki/Atomic/PRD) that was
>>> recently drafted says that other CPU architectures can be added as new
>>> community members join.  A perfectly fair and reasonable statement!
>>> However, it now leads me to ask a question of you.  Do you have formal
>>> ways for a new community member to join?  Is there an on-boarding
>>> document in place?  I ask because we already have community members
>>> willing to maintain other cpu architectures, particularly around ARM
>>> for IoT and ppc64le for containers.
>>>
>>> So aside from the work they have already done, such as request
>>> composes for these architectures and do testing, what else would you
>>> like to see in order for them to be official members?
>>>
>>
>> Hey Josh,
>>
>> We don't have anything official that I know of. For me it's all about
>> the following:
>>
>> 1 - do people hang out in IRC/mailing list and show up for meetings
>> 2 - do things get unbroken relatively quickly
> 
> I assume broken things get tickets or are somehow tracked?  Should
> interested members assign themselves said tickets?
> 

Yes. If something is broken a ticket will be opened and someone will
be assigned to it or we'll try to get someone to volunteer to work on
it.

>> 3 - does requested work get done in a timely manner
> 
> That one is interesting.  Requested by the WG?  That means the WG
> would have to know of said person before being able to request that
> they do something.  Somewhat of a chicken-egg scenario in the context
> of new contributors, yes?
> 
> Or did you mean something like you have a wishlist or outstanding
> ticket queue where new members could pick up items and work on them?
> That can be daunting for totally new members, but not unworkable.

I think what I was going for is: if new community members are proposing 
that we add some new thing that we haven't supported yet, then we
would need to make sure things get done in a timely manner for our
release cycles. One example would be that if we want to support
'atomic on rasberry pi', then we need to make sure we make progress on
the work and don't let it stagnate.

I guess this point is kind of ambiguous. What I was really trying to say
is that we want to see you around, making progress towards your/our
goals and *hopefully* using Atomic Host along the way.

> 
>> If you want to formally be a member of the WG then doing those three
>> things and requesting to be a formal member will most likely get you
>> there. You can formally request to be a member by opening a ticket
>> against our pagure instance.
>>
>> Note that formal WG membership doesn't really buy you much. We really
>> take all of our community involvement seriously and I don't think
>> we've ever not considered someones vote for something because they
>> weren't an official member. We are glad to have everyone!
>>
>> I hope this helps answer your question
> 
> It does, mostly.  That matches my experience in Fedora overall.
> 
> I have another follow-on question, but I think I'll digest this a bit
> before asking it.
> 
> josh
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Question on adding new contributors

2017-06-05 Thread Josh Boyer 
On Mon, Jun 5, 2017 at 4:55 PM, Dusty Mabe  wrote:
>
>
> On 06/05/2017 04:48 PM, Josh Boyer wrote:
>> Hi Atomic group,
>>
>> The Atomic PRD (https://fedoraproject.org/wiki/Atomic/PRD) that was
>> recently drafted says that other CPU architectures can be added as new
>> community members join.  A perfectly fair and reasonable statement!
>> However, it now leads me to ask a question of you.  Do you have formal
>> ways for a new community member to join?  Is there an on-boarding
>> document in place?  I ask because we already have community members
>> willing to maintain other cpu architectures, particularly around ARM
>> for IoT and ppc64le for containers.
>>
>> So aside from the work they have already done, such as request
>> composes for these architectures and do testing, what else would you
>> like to see in order for them to be official members?
>>
>
> Hey Josh,
>
> We don't have anything official that I know of. For me it's all about
> the following:
>
> 1 - do people hang out in IRC/mailing list and show up for meetings
> 2 - do things get unbroken relatively quickly

I assume broken things get tickets or are somehow tracked?  Should
interested members assign themselves said tickets?

> 3 - does requested work get done in a timely manner

That one is interesting.  Requested by the WG?  That means the WG
would have to know of said person before being able to request that
they do something.  Somewhat of a chicken-egg scenario in the context
of new contributors, yes?

Or did you mean something like you have a wishlist or outstanding
ticket queue where new members could pick up items and work on them?
That can be daunting for totally new members, but not unworkable.

> If you want to formally be a member of the WG then doing those three
> things and requesting to be a formal member will most likely get you
> there. You can formally request to be a member by opening a ticket
> against our pagure instance.
>
> Note that formal WG membership doesn't really buy you much. We really
> take all of our community involvement seriously and I don't think
> we've ever not considered someones vote for something because they
> weren't an official member. We are glad to have everyone!
>
> I hope this helps answer your question

It does, mostly.  That matches my experience in Fedora overall.

I have another follow-on question, but I think I'll digest this a bit
before asking it.

josh
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Question on adding new contributors

2017-06-05 Thread Josh Berkus 
On 06/05/2017 01:55 PM, Dusty Mabe wrote:
> 
> 
> On 06/05/2017 04:48 PM, Josh Boyer wrote:
>> Hi Atomic group,
>>
>> The Atomic PRD (https://fedoraproject.org/wiki/Atomic/PRD) that was
>> recently drafted says that other CPU architectures can be added as new
>> community members join.  A perfectly fair and reasonable statement!
>> However, it now leads me to ask a question of you.  Do you have formal
>> ways for a new community member to join?  Is there an on-boarding
>> document in place?  I ask because we already have community members
>> willing to maintain other cpu architectures, particularly around ARM
>> for IoT and ppc64le for containers.
>>
>> So aside from the work they have already done, such as request
>> composes for these architectures and do testing, what else would you
>> like to see in order for them to be official members?
>>
> 
> Hey Josh,
> 
> We don't have anything official that I know of. For me it's all about
> the following:
> 
> 1 - do people hang out in IRC/mailing list and show up for meetings
> 2 - do things get unbroken relatively quickly
> 3 - does requested work get done in a timely manner
> 
> If you want to formally be a member of the WG then doing those three
> things and requesting to be a formal member will most likely get you
> there. You can formally request to be a member by opening a ticket 
> against our pagure instance.
> 
> Note that formal WG membership doesn't really buy you much. We really
> take all of our community involvement seriously and I don't think
> we've ever not considered someones vote for something because they
> weren't an official member. We are glad to have everyone!
> 
> I hope this helps answer your question

Hey, we could put up a wiki page with all of the above, no?


-- 
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Question on adding new contributors

2017-06-05 Thread Dusty Mabe 


On 06/05/2017 04:48 PM, Josh Boyer wrote:
> Hi Atomic group,
> 
> The Atomic PRD (https://fedoraproject.org/wiki/Atomic/PRD) that was
> recently drafted says that other CPU architectures can be added as new
> community members join.  A perfectly fair and reasonable statement!
> However, it now leads me to ask a question of you.  Do you have formal
> ways for a new community member to join?  Is there an on-boarding
> document in place?  I ask because we already have community members
> willing to maintain other cpu architectures, particularly around ARM
> for IoT and ppc64le for containers.
> 
> So aside from the work they have already done, such as request
> composes for these architectures and do testing, what else would you
> like to see in order for them to be official members?
> 

Hey Josh,

We don't have anything official that I know of. For me it's all about
the following:

1 - do people hang out in IRC/mailing list and show up for meetings
2 - do things get unbroken relatively quickly
3 - does requested work get done in a timely manner

If you want to formally be a member of the WG then doing those three
things and requesting to be a formal member will most likely get you
there. You can formally request to be a member by opening a ticket 
against our pagure instance.

Note that formal WG membership doesn't really buy you much. We really
take all of our community involvement seriously and I don't think
we've ever not considered someones vote for something because they
weren't an official member. We are glad to have everyone!

I hope this helps answer your question
Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [atomic-devel] Changing partitioning defaults discussion

2017-06-05 Thread Dusty Mabe 


On 06/05/2017 03:12 PM, Dusty Mabe wrote:
> 
> 
> On 06/05/2017 02:19 PM, Colin Walters wrote:
>> On Mon, Jun 5, 2017, at 01:58 PM, Dusty Mabe wrote:
>>>
>>> One qualification - we use overlay2 by default, but we are going to be
>>> placing all of /var/lib/docker/ on its own filesystem:
>>>
>>> $ cat /etc/sysconfig/docker-storage-setup 
>>> # Edit this file to override any configuration options specified in
>>> # /usr/share/container-storage-setup/container-storage-setup.
>>> #
>>> # For more details refer to "man container-storage-setup"
>>> STORAGE_DRIVER=overlay2
>>> CONTAINER_ROOT_LV_NAME=docker-root-lv
>>> CONTAINER_ROOT_LV_MOUNT_PATH=/var/lib/docker
>>> GROWPART=true
>>
>> Yes.  I think I'm proposing we keep that
>> behavior for F26, and change rawhide to remove the separate LV
>> by default.
> 
> OK. To be clear, all of this is for rawhide and onward, not F26. Got
> it.
> 
> If we are going to officially make that proposal can we open a ticket
> for it in the atomic-wg pagure? I know many of us have talked about
> it, but I would like to formalize that as our strategy.
> 

Note this partially plays into https://pagure.io/atomic-wg/issue/281
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: 2wk atomic release candidate: 20170605

2017-06-05 Thread Dusty Mabe 


On 06/05/2017 09:23 AM, Dusty Mabe wrote:
> 
> We are going to attempt to release the 20170605 images tomorrow. 
> These images contain the following ostree version/commit:
> 
> 25.127
> cdd359911de49f3a8199ffd41a9894019562001d6cf9be66e1894c31b6fa1c66
> 

Correction:

25.137
0ed61d7441eddf96e6a98de4f10f4675268c7888b6d2b8a405b8c21fe6c92d23
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

2wk atomic release candidate: 20170605

2017-06-05 Thread Dusty Mabe 

We are going to attempt to release the 20170605 images tomorrow. 
These images contain the following ostree version/commit:

25.127
cdd359911de49f3a8199ffd41a9894019562001d6cf9be66e1894c31b6fa1c66

The atomic host VM images are here:

https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170605.0/compose/CloudImages/x86_64/images/

The ISO image is here:

https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170605.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170605.0.iso

The AMIs are here:

Fedora-Atomic-25-20170605.0.x86_64  EC2 (ap-northeast-1) ami-27a5a640hvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (ap-southeast-1) ami-ba52d2d9hvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (ap-southeast-2) ami-0dabbc6ehvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (eu-central-1)   ami-5266bc3dhvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (eu-west-1)  ami-6dd7c40bhvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (sa-east-1)  ami-18d0b974hvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-east-1)  ami-56491940hvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-west-1)  ami-82ad8ee2hvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-west-2)  ami-bc1619c5hvm  
standard   
Fedora-Atomic-25-20170605.0.x86_64  EC2 (ap-northeast-1) ami-8ea4a7e9hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (ap-southeast-1) ami-f451d197hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (ap-southeast-2) ami-9baabdf8hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (eu-central-1)   ami-a76cb6c8hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (eu-west-1)  ami-2dd4c74bhvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-east-1)  ami-6f481879hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-west-1)  ami-33ad8e53hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-west-1)  ami-33ad8e53hvm  
gp2
Fedora-Atomic-25-20170605.0.x86_64  EC2 (us-west-2)  ami-0719167ehvm  
gp2

The diff between this and the previous released version is:

ostree diff commit old: 
cdd359911de49f3a8199ffd41a9894019562001d6cf9be66e1894c31b6fa1c66
ostree diff commit new: 
0ed61d7441eddf96e6a98de4f10f4675268c7888b6d2b8a405b8c21fe6c92d23
Upgraded:
  acl 2.2.52-11.fc24.x86_64 -> 2.2.52-12.fc25.x86_64
  atomic 1.17.1-4.fc25.x86_64 -> 1.17.2-1.fc25.x86_64
  bubblewrap 0.1.7-1.fc25.x86_64 -> 0.1.8-1.fc25.x86_64
  container-selinux 2:2.10-1.fc25.noarch -> 2:2.14-1.fc25.noarch
  dhcp-client 12:4.3.5-1.fc25.x86_64 -> 12:4.3.5-2.fc25.x86_64
  dhcp-common 12:4.3.5-1.fc25.noarch -> 12:4.3.5-2.fc25.noarch
  dhcp-libs 12:4.3.5-1.fc25.x86_64 -> 12:4.3.5-2.fc25.x86_64
  freetype 2.6.5-7.fc25.x86_64 -> 2.6.5-9.fc25.x86_64
  glusterfs 3.10.1-1.fc25.x86_64 -> 3.10.2-1.fc25.x86_64
  glusterfs-client-xlators 3.10.1-1.fc25.x86_64 -> 3.10.2-1.fc25.x86_64
  glusterfs-fuse 3.10.1-1.fc25.x86_64 -> 3.10.2-1.fc25.x86_64
  glusterfs-libs 3.10.1-1.fc25.x86_64 -> 3.10.2-1.fc25.x86_64
  gssproxy 0.7.0-3.fc25.x86_64 -> 0.7.0-9.fc25.x86_64
  kernel 4.10.15-200.fc25.x86_64 -> 4.11.3-200.fc25.x86_64
  kernel-core 4.10.15-200.fc25.x86_64 -> 4.11.3-200.fc25.x86_64
  kernel-modules 4.10.15-200.fc25.x86_64 -> 4.11.3-200.fc25.x86_64
  libacl 2.2.52-11.fc24.x86_64 -> 2.2.52-12.fc25.x86_64
  libsolv 0.6.27-1.fc25.x86_64 -> 0.6.27-2.fc25.x86_64
  lua-libs 5.3.4-1.fc25.x86_64 -> 5.3.4-3.fc25.x86_64
  nss 3.30.2-1.0.fc25.x86_64 -> 3.30.2-1.1.fc25.x86_64
  nss-sysinit 3.30.2-1.0.fc25.x86_64 -> 3.30.2-1.1.fc25.x86_64
  nss-tools 3.30.2-1.0.fc25.x86_64 -> 3.30.2-1.1.fc25.x86_64
  p11-kit 0.23.2-3.fc25.x86_64 -> 0.23.2-4.fc25.x86_64
  p11-kit-trust 0.23.2-3.fc25.x86_64 -> 0.23.2-4.fc25.x86_64
  runc 1:1.0.0-5.rc2.gitc91b5be.fc25.x86_64 -> 
1:1.0.0-6.git75f8da7.fc25.1.x86_64
  screen 4.5.1-1.fc25.x86_64 -> 4.5.1-2.fc25.x86_64
  strace 4.16-1.fc25.x86_64 -> 4.17-1.fc25.x86_64
  sudo 1.8.19p2-1.fc25.x86_64 -> 1.8.20p2-1.fc25.x86_64
  systemd 231-14.fc25.x86_64 -> 231-15.fc25.x86_64
  systemd-container 231-14.fc25.x86_64 -> 231-15.fc25.x86_64
  systemd-libs 231-14.fc25.x86_64 -> 231-15.fc25.x86_64
  systemd-pam 231-14.fc25.x86_64 -> 231-15.fc25.x86_64
  systemd-udev 231-14.fc25.x86_64 -> 231-15.fc25.x86_64
  vim-minimal 2:8.0.596-1.fc25.x86_64 -> 2:8.0.600-1.fc25.x86_64


Notable updates are the kernel, systemd, bubblewrap, and runc.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org