Date   

Re: cdCON sponsorship prospectus & registration is open!

Dana Everitt <dana@...>
 

Hi Jacqueline,

Thanks for sharing the sponsorship prospectus! 

Would you be sharing the leads for everyone who views our virtual booth? 
And if so, do they have the option to opt-out of sharing their contact info, and what percent of attendees do you expect to opt-out?

Best,
Dana

Dana Everitt | Manager, Event Marketing
Datadog, Inc. | dana@datadoghq.com 
@datadoghq | www.datadoghq.com 

Register for free!


On Wed, Jul 22, 2020 at 6:49 PM Jacqueline Salinas <jsalinas@...> wrote:
Hello all, 

I hope this email finds you well! We have some VERY exciting news from the CDF Outreach and Events team...drum roll, please! 

The CDF flagship event, cdCON, is ready to start selling sponsorships & registrations. 

Join the CD Foundation for a two-day virtual event focused on improving the world’s capacity to deliver software with security and speed. Become part of the conversation that drives continuous delivery by meeting peers, sharing ideas and talking to industry leaders on all things software delivery and DevOps.

Download the prospectus here! Reach out to jsalinas@... if you are interested in sponsoring cdCON. 

Here is a brief overview of the type of sponsorships we have available: 
  • 2 (1) Diamond - THANK YOU JFROG! 
  • 2 Platinum
  • 5 Gold 
  • 5 Silver
  • UNLIMITED Start-up & End User

Share on social media the good news! 
Jacqueline Salinas 
Continuous Delivery Foundation
Director of Ecosystem & Community
408 218 0667




Re: CD Foundation program management

Michael Winser
 

Welcome Gale!


On Mon, Jul 27, 2020, 11:32 PM Brian Warner <bwarner@...> wrote:
Governing board and TOC,

As most of you know, Dan Lopez left the Linux Foundation to pursue other opportunities. I'd like to introduce Gale McCommons, who will be replacing Dan as program manager for CDF.

Gale is on my team at the Linux Foundation, and has already begun working with Tracy Miranda and Jacque Salinas on a variety of CDF items. Going forward, Gale and I will both be helping to reduce the backlog of todos, as well as support the project on ongoing work. Generally speaking, I'll be focused on the backlog and Gale will be helping with the ongoing program management work.

The best way to reach us is by emailing the operations@... alias. This is configured to forward to both of us.

Thank you, and we're looking forward to working with you,
Brian


--

Brian Warner
The Linux Foundation
+1 724 301-6171


CD Foundation program management

 

Governing board and TOC,

As most of you know, Dan Lopez left the Linux Foundation to pursue other opportunities. I'd like to introduce Gale McCommons, who will be replacing Dan as program manager for CDF.

Gale is on my team at the Linux Foundation, and has already begun working with Tracy Miranda and Jacque Salinas on a variety of CDF items. Going forward, Gale and I will both be helping to reduce the backlog of todos, as well as support the project on ongoing work. Generally speaking, I'll be focused on the backlog and Gale will be helping with the ongoing program management work.

The best way to reach us is by emailing the operations@... alias. This is configured to forward to both of us.

Thank you, and we're looking forward to working with you,
Brian


--

Brian Warner
The Linux Foundation
+1 724 301-6171


Re: [VOTE] Jenkins Graduation

Olivier Vernin
 

Non binding +1 :-) 

Olivier

---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---


On Fri, Jul 24, 2020, at 7:18 PM, TracyRagan wrote:
+1 from me. 

On Fri, Jul 24, 2020 at 11:14 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Reminder: If you're on the to: line, we still do not have your vote.

Please vote on the Jenkins graduation ASAP!

On Tue, Jul 21, 2020 at 10:49 AM Tara Hernandez <tarahernandez@...> wrote:
+1

On Tue, Jul 21, 2020 at 8:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc





--
Tara Hernandez
Engineering Manager Google Cloud






--
Kind Regards,

Tracy Ragan
CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558
Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub
We make microservices easy. 




Re: [VOTE] Jenkins Graduation

TracyRagan
 

+1 from me. 

On Fri, Jul 24, 2020 at 11:14 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Reminder: If you're on the to: line, we still do not have your vote.

Please vote on the Jenkins graduation ASAP!

On Tue, Jul 21, 2020 at 10:49 AM Tara Hernandez <tarahernandez@...> wrote:
+1

On Tue, Jul 21, 2020 at 8:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc



--
Tara Hernandez
Engineering Manager Google Cloud





--
Kind Regards,

Tracy Ragan
CEO and Co-Founder / DeployHub / tel: + 1.505.424.6440/ mob: +1.505.780.0558
Follow me on: Blog / Twitter Facebook / LinkedIn / YouTube / GitHub
We make microservices easy. 





Re: [VOTE] Jenkins Graduation

Dan Lorenc <dlorenc@...>
 

Reminder: If you're on the to: line, we still do not have your vote.

Please vote on the Jenkins graduation ASAP!

On Tue, Jul 21, 2020 at 10:49 AM Tara Hernandez <tarahernandez@...> wrote:
+1

On Tue, Jul 21, 2020 at 8:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc



--
Tara Hernandez
Engineering Manager Google Cloud




cdCON sponsorship prospectus & registration is open!

Jacque Salinas
 

Hello all, 

I hope this email finds you well! We have some VERY exciting news from the CDF Outreach and Events team...drum roll, please! 

The CDF flagship event, cdCON, is ready to start selling sponsorships & registrations. 

Join the CD Foundation for a two-day virtual event focused on improving the world’s capacity to deliver software with security and speed. Become part of the conversation that drives continuous delivery by meeting peers, sharing ideas and talking to industry leaders on all things software delivery and DevOps.

Download the prospectus here! Reach out to jsalinas@... if you are interested in sponsoring cdCON. 

Here is a brief overview of the type of sponsorships we have available: 
  • 2 (1) Diamond - THANK YOU JFROG! 
  • 2 Platinum
  • 5 Gold 
  • 5 Silver
  • UNLIMITED Start-up & End User

Share on social media the good news! 

  • https://twitter.com/CDeliveryFdn/status/1285992715490955264?s=20
  • https://www.linkedin.com/feed/update/urn:li:activity:6691759409393098752
  •  
Jacqueline Salinas 
Continuous Delivery Foundation
Director of Ecosystem & Community
408 218 0667




Re: [VOTE] Jenkins Graduation

Tara Hernandez
 

+1

On Tue, Jul 21, 2020 at 8:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc



--
Tara Hernandez
Engineering Manager Google Cloud




Re: [VOTE] Jenkins Graduation

Oleg Nenashev
 

Non-binding +1. Thanks to all contributors for reviews and feedback during the application prepwork!


On Tue, Jul 21, 2020 at 5:46 PM Alejandro Saucedo <as@...> wrote:
Non-binding +1!


Best wishes,


Alejandro Saucedo

Engineering Director (Machine Learning) at Seldon


Gartner Cool Vendor 2020 in AI Core Technologies - read more

 

Seldon Technologies Ltd, Rise London (map). Registered in England & Wales, No. 9188032. VAT GB 258424587. Privacy Policy.



On Tue, Jul 21, 2020 at 4:40 PM Marky Jackson <marky.r.jackson@...> wrote:
Non-binding +1

On Jul 21, 2020, at 8:38 AM, Fred Blaise <fblaise@...> wrote:


Non-binding +1 :-)

On Tue, Jul 21, 2020 at 5:27 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc


Re: [VOTE] Jenkins Graduation

Alejandro Saucedo
 

Non-binding +1!


Best wishes,


Alejandro Saucedo

Engineering Director (Machine Learning) at Seldon


Gartner Cool Vendor 2020 in AI Core Technologies - read more

 

Seldon Technologies Ltd, Rise London (map). Registered in England & Wales, No. 9188032. VAT GB 258424587. Privacy Policy.



On Tue, Jul 21, 2020 at 4:40 PM Marky Jackson <marky.r.jackson@...> wrote:
Non-binding +1

On Jul 21, 2020, at 8:38 AM, Fred Blaise <fblaise@...> wrote:


Non-binding +1 :-)

On Tue, Jul 21, 2020 at 5:27 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc


Re: [VOTE] Jenkins Graduation

Marky Jackson <marky.r.jackson@...>
 

Non-binding +1

On Jul 21, 2020, at 8:38 AM, Fred Blaise <fblaise@...> wrote:


Non-binding +1 :-)

On Tue, Jul 21, 2020 at 5:27 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc


Re: [VOTE] Jenkins Graduation

Fred Blaise
 

Non-binding +1 :-)


On Tue, Jul 21, 2020 at 5:27 PM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc


Re: [VOTE] Jenkins Graduation

Kohsuke Kawaguchi
 

+1


On Tue, Jul 21, 2020 at 8:27 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc



--
Kohsuke Kawaguchi


[VOTE] Jenkins Graduation

Dan Lorenc <dlorenc@...>
 

Hey Everyone,

As discussed in today's TOC call, the Jenkins graduation proposal is ready for a vote. The criteria we have established are available for reference here.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

I'll start with my own +1.

Please try to get your votes in by the end of this week, July 24th.

Dan Lorenc


Reminder: Review Jenkins Graduation Criteria

Dan Lorenc <dlorenc@...>
 

Reminder everyone, we'll be discussing the Jenkins project Graduation proposal next week in our usual slot. Please review the proposal here: https://docs.google.com/document/d/1Ldmtny6OfEtQlCqdFWqq9Z25cxkZFX6yNiRqOOxo77c/edit#heading=h.ap7s1hy35euf


Dan Lorenc


Re: Application: Jenkins project graduation

Dan Lorenc <dlorenc@...>
 

Thanks Oleg! I'll add this to the agenda for next week. I'll ask that everyone on the TOC please take the time to review in the next week or so.

Dan Lorenc

On Mon, Jul 13, 2020 at 1:46 PM Oleg Nenashev <o.v.nenashev@...> wrote:

Dear CDF TOC,


On behalf of the Jenkins Governance Board, we would like to initiate the graduation stage review for the Jenkins project. Over the past months we have invested time to align the project with the definitions, expectations and acceptance criteria of the CDF Graduated Stage as of July 13, 2020. We believe that the Jenkins project is now fully compliant with the criteria.


To assist with the review, we prepared a CDF Graduation Compliance checklist for the Jenkins project. It provides details about each compliance criteria. You can find this checklist in this Google Doc.


We ask the TOC to perform a formal review of our application and schedule a time where we can present to the committee and answer any questions arising. Please let us know if any additional information is required to perform the evaluation, we will make sure to provide it promptly.


Thanks in advance,

Oleg Nenashev, Alex Earl, Ullrich Hafner

Jenkins Governance Board Members



Application: Jenkins project graduation

Oleg Nenashev
 

Dear CDF TOC,


On behalf of the Jenkins Governance Board, we would like to initiate the graduation stage review for the Jenkins project. Over the past months we have invested time to align the project with the definitions, expectations and acceptance criteria of the CDF Graduated Stage as of July 13, 2020. We believe that the Jenkins project is now fully compliant with the criteria.


To assist with the review, we prepared a CDF Graduation Compliance checklist for the Jenkins project. It provides details about each compliance criteria. You can find this checklist in this Google Doc.


We ask the TOC to perform a formal review of our application and schedule a time where we can present to the committee and answer any questions arising. Please let us know if any additional information is required to perform the evaluation, we will make sure to provide it promptly.


Thanks in advance,

Oleg Nenashev, Alex Earl, Ullrich Hafner

Jenkins Governance Board Members



Re: GitHub Hygiene

 

Thanks Oleg, if you do decide to migrate the CLA platform, I'm happy to help. It's pretty straightforward on our end.

Best,
Brian



On Mon, Jul 13, 2020 at 3:20 AM Oleg Nenashev <o.v.nenashev@...> wrote:
Hi,

The Jenkins project uses Individual and Company CLAs (see this repo). This CLA is required ONLY for contributors who want to get special permissions (i.e. Jenkins core repo permissions, Security team membership, access to social media and YouTube accounts, etc.). We do not require the CLA to be signed by plugin maintainers or by common contributors.

In any case the Jenkins CLA process is subject to rework once the project assets are officially transferred to CDF. Our CLA process is also pretty tedious and time-consuming for signees and board members who process CLAs and verify that the submitted documents are correct and, in the case of Company CLAs, legit. The CLA doc is also quite obsolete, and it does not fully represent the current community processes (e.g. no reference to Jenkins code of conduct which was introduced after CLA). Switching to EasyCLA is one of the options we discussed last time, and I believe there was a consensus that we'd like to explore that in the future. According to the blogs and video recordings I watched, it is a pretty convenient tool if a project wants to enforce CLA.

Best regards,
Oleg Nenashev


On Fri, Jul 10, 2020 at 8:15 PM Jithin Emanuel <jithin1987@...> wrote:
Screwdriver used to have a CLA signer bot for making contributions, but we got rid of it and streamlined across all Verizon Media open source projects to have this Pull Request template. https://github.com/screwdriver-cd/.github/blob/master/PULL_REQUEST_TEMPLATE.md#license

--
Jithin

On Fri, Jul 10, 2020 at 8:28 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Jumping back up thread:

We don't have a blanket CLA policy for the CDF - we allow projects to choose what they want. The LF has tooling in place (EasyCLA) to make it easy for projects to use a CLA if they choose (Tekton uses this for example). Jenkins X and Spinnaker on the other hand, do not use CLAs. As far as recommendations/reasons to use one or not use one - we'd need to ask LF/corporate legal teams for their recommendations.

Repo access controls are now a bit easier - thanks Brian! We could setup automation on this (check out how Tekton does this: https://github.com/tektoncd/community/tree/master/org), but it may be overkill. 

Dan Lorenc

On Tue, Jul 7, 2020 at 2:57 PM Tara Hernandez <tarahernandez@...> wrote:
Damn, had forgotten all about those (so, yay for me adding it to the notes against that eventuality)

:)

I don't have a list of repos per se,  this was more around a general policy question that arose out of another discussion -- do we have any kind of consistent policy or recommended best practice for our projects with regards to CLAs and should the CDF be handling that on behalf of the projects.  Put another way, is there a reason NOT to just do it everywhere?  

The second item also came up during that discussion because we realized the CDF repos were pretty locked down and nobody seemed to have admin access other than Dan (and now Brian), so getting some teams and roles in there would be lovely.

On Tue, Jul 7, 2020 at 6:07 AM Dan Lorenc <dlorenc@...> wrote:
Tara had a couple TOC agenda items for today:
  • [tara] Need a CLA or similar for ambassadors/contributors to clarify contributions from individuals vs. corps 
Tara, could you clarify which repos you'd like to get the CLA setup on? We should be able to use EasyCLA for this.
I agree here. +Brian Warner - do you have the admin permissions on github.com/cdfoundation? Would you mind adding me so I can setup teams/permissions?

Dan Lorenc


--
Tara Hernandez
Engineering Manager Google Cloud





--
Thanks
Jithin Emmanuel



--

Brian Warner
The Linux Foundation
+1 724 301-6171


Re: GitHub Hygiene

Oleg Nenashev
 

Hi,

The Jenkins project uses Individual and Company CLAs (see this repo). This CLA is required ONLY for contributors who want to get special permissions (i.e. Jenkins core repo permissions, Security team membership, access to social media and YouTube accounts, etc.). We do not require the CLA to be signed by plugin maintainers or by common contributors.

In any case the Jenkins CLA process is subject to rework once the project assets are officially transferred to CDF. Our CLA process is also pretty tedious and time-consuming for signees and board members who process CLAs and verify that the submitted documents are correct and, in the case of Company CLAs, legit. The CLA doc is also quite obsolete, and it does not fully represent the current community processes (e.g. no reference to Jenkins code of conduct which was introduced after CLA). Switching to EasyCLA is one of the options we discussed last time, and I believe there was a consensus that we'd like to explore that in the future. According to the blogs and video recordings I watched, it is a pretty convenient tool if a project wants to enforce CLA.

Best regards,
Oleg Nenashev


On Fri, Jul 10, 2020 at 8:15 PM Jithin Emanuel <jithin1987@...> wrote:
Screwdriver used to have a CLA signer bot for making contributions, but we got rid of it and streamlined across all Verizon Media open source projects to have this Pull Request template. https://github.com/screwdriver-cd/.github/blob/master/PULL_REQUEST_TEMPLATE.md#license

--
Jithin

On Fri, Jul 10, 2020 at 8:28 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Jumping back up thread:

We don't have a blanket CLA policy for the CDF - we allow projects to choose what they want. The LF has tooling in place (EasyCLA) to make it easy for projects to use a CLA if they choose (Tekton uses this for example). Jenkins X and Spinnaker on the other hand, do not use CLAs. As far as recommendations/reasons to use one or not use one - we'd need to ask LF/corporate legal teams for their recommendations.

Repo access controls are now a bit easier - thanks Brian! We could setup automation on this (check out how Tekton does this: https://github.com/tektoncd/community/tree/master/org), but it may be overkill. 

Dan Lorenc

On Tue, Jul 7, 2020 at 2:57 PM Tara Hernandez <tarahernandez@...> wrote:
Damn, had forgotten all about those (so, yay for me adding it to the notes against that eventuality)

:)

I don't have a list of repos per se,  this was more around a general policy question that arose out of another discussion -- do we have any kind of consistent policy or recommended best practice for our projects with regards to CLAs and should the CDF be handling that on behalf of the projects.  Put another way, is there a reason NOT to just do it everywhere?  

The second item also came up during that discussion because we realized the CDF repos were pretty locked down and nobody seemed to have admin access other than Dan (and now Brian), so getting some teams and roles in there would be lovely.

On Tue, Jul 7, 2020 at 6:07 AM Dan Lorenc <dlorenc@...> wrote:
Tara had a couple TOC agenda items for today:
  • [tara] Need a CLA or similar for ambassadors/contributors to clarify contributions from individuals vs. corps 
Tara, could you clarify which repos you'd like to get the CLA setup on? We should be able to use EasyCLA for this.
I agree here. +Brian Warner - do you have the admin permissions on github.com/cdfoundation? Would you mind adding me so I can setup teams/permissions?

Dan Lorenc


--
Tara Hernandez
Engineering Manager Google Cloud





--
Thanks
Jithin Emmanuel


Re: GitHub Hygiene

Jithin Emanuel
 

Screwdriver used to have a CLA signer bot for making contributions, but we got rid of it and streamlined across all Verizon Media open source projects to have this Pull Request template. https://github.com/screwdriver-cd/.github/blob/master/PULL_REQUEST_TEMPLATE.md#license

--
Jithin


On Fri, Jul 10, 2020 at 8:28 AM Dan Lorenc via lists.cd.foundation <dlorenc=google.com@...> wrote:
Jumping back up thread:

We don't have a blanket CLA policy for the CDF - we allow projects to choose what they want. The LF has tooling in place (EasyCLA) to make it easy for projects to use a CLA if they choose (Tekton uses this for example). Jenkins X and Spinnaker on the other hand, do not use CLAs. As far as recommendations/reasons to use one or not use one - we'd need to ask LF/corporate legal teams for their recommendations.

Repo access controls are now a bit easier - thanks Brian! We could setup automation on this (check out how Tekton does this: https://github.com/tektoncd/community/tree/master/org), but it may be overkill. 

Dan Lorenc

On Tue, Jul 7, 2020 at 2:57 PM Tara Hernandez <tarahernandez@...> wrote:
Damn, had forgotten all about those (so, yay for me adding it to the notes against that eventuality)

:)

I don't have a list of repos per se,  this was more around a general policy question that arose out of another discussion -- do we have any kind of consistent policy or recommended best practice for our projects with regards to CLAs and should the CDF be handling that on behalf of the projects.  Put another way, is there a reason NOT to just do it everywhere?  

The second item also came up during that discussion because we realized the CDF repos were pretty locked down and nobody seemed to have admin access other than Dan (and now Brian), so getting some teams and roles in there would be lovely.

On Tue, Jul 7, 2020 at 6:07 AM Dan Lorenc <dlorenc@...> wrote:
Tara had a couple TOC agenda items for today:
  • [tara] Need a CLA or similar for ambassadors/contributors to clarify contributions from individuals vs. corps 
Tara, could you clarify which repos you'd like to get the CLA setup on? We should be able to use EasyCLA for this.
I agree here. +Brian Warner - do you have the admin permissions on github.com/cdfoundation? Would you mind adding me so I can setup teams/permissions?

Dan Lorenc


--
Tara Hernandez
Engineering Manager Google Cloud





--
Thanks
Jithin Emmanuel

361 - 380 of 845