Apt modify repo


#1

For those apt cookbook users:
sometimesfood has implemented an ability for apt repo’s to be
modified. Currently you have to remove then add if you want to make a
change.
Check it out:


πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://hedgehogshiatus.com


#2

Is there an associated ticket with this?

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, Dec 9, 2011 at 1:33 AM, Hedge Hog hedgehogshiatus@gmail.com wrote:

For those apt cookbook users:
sometimesfood has implemented an ability for apt repo’s to be
modified. Currently you have to remove then add if you want to make a
change.
Check it out:
https://github.com/cookbooks/apt/pull/10


πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://hedgehogshiatus.com


#3

Hi Matt,

On Friday, 9 December 2011, Matt Ray matt@opscode.com wrote:

Is there an associated ticket with this?

Only a GitHub ticket for now:

(This is also referenced in the pull request.)

Do you want me to create an issue on JIRA?

I have just joined the newly formed apt cookbook team, so I’m not
quite familiar with the current development process for cookbooks yet.

Sebastian


#4

The rationale for a ticket in JIRA is that it helps us track tickets
and patches for release notes and giving credit.
http://wiki.opscode.com/display/chef/How+to+Contribute#HowtoContribute-WhydoIneedtohaveaticket
I see you’re already an approved contributor, so after the ticket gets
triaged I’d expect the merge and publish pretty quick.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, Dec 9, 2011 at 10:14 AM, Sebastian Boehm
sebastian@sometimesfood.org wrote:

Hi Matt,

On Friday, 9 December 2011, Matt Ray matt@opscode.com wrote:

Is there an associated ticket with this?

Only a GitHub ticket for now:
https://github.com/cookbooks/apt/issues/8

(This is also referenced in the pull request.)

Do you want me to create an issue on JIRA?

I have just joined the newly formed apt cookbook team, so I’m not
quite familiar with the current development process for cookbooks yet.

Sebastian


#5

Hi,

On 9 December 2011 17:25, Matt Ray matt@opscode.com wrote:

The rationale for a ticket in JIRA is that it helps us track tickets
and patches for release notes and giving credit.

Ok, I’ll open a JIRA ticket later.

I was under the impression that you used a different development
process for cookbooks. If it’s just the same as for the rest of chef
and you don’t merge changes from https://github.com/cookbooks, I’ll
just revert to submitting regular JIRA tickets and pull requests
instead of commiting to cookbooks/apt on GitHub.

Sebastian


#6

On Fri, Dec 9, 2011 at 1:33 AM, Hedge Hog hedgehogshiatus@gmail.com wrote:

https://github.com/cookbooks/apt/pull/10

On Fri, Dec 9, 2011 at 9:36 AM, Matt Ray matt@opscode.com wrote:

Is there an associated ticket with this?

On Fri, Dec 9, 2011 at 11:14 AM, Sebastian Boehm
sebastian@sometimesfood.org wrote:

Only a GitHub ticket for now:
https://github.com/cookbooks/apt/issues/8

For the sake of clarity for those new to the list, this is a pull
request and github issue in the ‘cookbooks’ GitHub account, which is
completely separate from the Opscode Cookbooks at
http://github.com/opscode/cookbooks and our ticketing at
http://tickets.opscode.com

It would be great if the Website/Blog link for that repository pointed
at a static page somewhere that outlined its purpose, how to
contribute to it, and how it differs from the Opscode cookbook
repository regarding content, source and contribution.

Bryan


#7

On Sat, Dec 10, 2011 at 3:37 PM, Bryan McLellan btm@loftninjas.org wrote:

On Fri, Dec 9, 2011 at 1:33 AM, Hedge Hog hedgehogshiatus@gmail.com wrote:

https://github.com/cookbooks/apt/pull/10

On Fri, Dec 9, 2011 at 9:36 AM, Matt Ray matt@opscode.com wrote:

Is there an associated ticket with this?

On Fri, Dec 9, 2011 at 11:14 AM, Sebastian Boehm
sebastian@sometimesfood.org wrote:

Only a GitHub ticket for now:
https://github.com/cookbooks/apt/issues/8

For the sake of clarity for those new to the list, this is a pull
request and github issue in the ‘cookbooks’ GitHub account, which is
completely separate from the Opscode Cookbooks at
http://github.com/opscode/cookbooks and our ticketing at
http://tickets.opscode.com

It would be great if the Website/Blog link for that repository pointed
at a static page somewhere that outlined its purpose, how to
contribute to it, and how it differs from the Opscode cookbook
repository regarding content, source and contribution.

Bryan is right we should have an about repo that is a github-pages site.
Essentially one description of the the problems tackled by
github.com/cookbooks is described in the following exchange (rberger
not assoc with any cookbooks teams as far as I am aware, he just
describes an issue many have identified for some time):
http://help.opscode.com/discussions/questions/531-installing-cookbooks-from-non-community-sites

This also makes clear why Opscode won’t, can’t and arguably shouldn’t
advocate for use of one of:

They have SLAs to deliver on and they can only do that if they have
the fully control that people paying for the SLA are demanding by,
well, paying for a SLA :slight_smile:
It’s not personal - just business.

Of course anybody can fork:

make their changes on top and offer whatever SLA they feel they can.

HTH clarify

Bryan


πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://hedgehogshiatus.com


#8

Hi,

Since I’m not a fan of duplicating efforts, I just
submitted JIRA tickets for all of my contributions (COOK-888 up to
COOK-891).

Here’s the relevant ticket for the aforementioned pull request:
http://tickets.opscode.com/browse/COOK-889

Sorry for the confusion, I thought that there was some kind of
agreement between Opscode and the github.com/cookbooks project to
merge back changes after code review. Thanks for clarifying.

Sebastian


#9

On Sat, Dec 10, 2011 at 9:59 PM, Sebastian Boehm
sebastian@sometimesfood.org wrote:

Hi,

Since I’m not a fan of duplicating efforts, I just
submitted JIRA tickets for all of my contributions (COOK-888 up to
COOK-891).

Here’s the relevant ticket for the aforementioned pull request:
http://tickets.opscode.com/browse/COOK-889

Sorry for the confusion, I thought that there was some kind of
agreement between Opscode and the github.com/cookbooks project to
merge back changes after code review. Thanks for clarifying.

No apologies needed!
There are many, many opscode/cookbooks forks on github, this is just
one fork that simply refactors out folders into repos.
In practical terms we do no more or less than anyone who forks
opscode/cookbooks so there is no reason to expect Opscode to regard
cokkbooks/ more or less highly than any other
/cookbooks fork.
Where cookbooks/ does differ is in not limiting itself to
opscode as upstream for the reasons mentioned earlier. In addition,
and this is solely due to Githubs ‘social coding’ tools, we allow for
specialist teams to form if they want - and that is determined by
community interest alone :slight_smile:

Best wishes.

Sebastian


πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://hedgehogshiatus.com