[...] please find attached Aporia Green FAQ to include as an appendix to your bid as discussed, coupled with the following form of words to appear somewhere under the heading of your intended bid work-package for evaluation/ethnography/dissemination:
“This work-package will be managed in collaboration with Aporia Green (see appendix X) which has been emerging as a community-driven initiative within the [...] Programme’s [...] Community, complementary to the [...] Project Team (Support 1) and the [...] Team (Support 2) ongoing activities”
then simply allocate the amount you think is reasonable to cover this work package as a proportion of your overall budget. depending on take up across successful (and almost successful projects), the amounts allocated by individual project bids will contribute to Aporia Green’s pooled resources as a whole which, all being well, should extend to recruiting of specialist ethnographers across projects who would otherwise not be available piecemeal.
hope this keeps bid writing simple – and relatively homogenous for the bid markers over the coming period – this message is being blind copied to 7 individual projects, 5 from the emerge community and 2 without as far as I am aware. however, if you know of any other bids that may be interested in taking up this option with us, please feel free to pass this open invitation to them also [...]
[...] for the record, dear [...], people throughout the community need to know a couple of things arising out of this post and ensuing commentary – so here goes telling it (online) as it is.
first, for the avoidance of doubt, please take this response by way of notice that this set of posts is being flagged as both defamatory and offensive to the community member being wrongfully accused of artificially inflating the hit count relating to the tag cloud instances in question.
in this sense, am suggesting that both the programme manager and the project director (not to name and shame) consult their respective line managers as to how best to offer official redress – the chain of command may also wish to consult [...] Legal on the matters arising, particularly with regard to the careful phrasing of this here comment which is being posted publicly in formal response to said accusations.
additionally, the chain of command may wish to consult [...] on related risk management matters arising out of having procured and deployed elgg open source software thus far. for example, the attempted reverse-engineering of elgg specific algorithms may be in breach of existing software licensing agreements – access to source code does not usually extend to potential abuse of author/developers’ moral rights.
notwithstanding, it is important that this set of posts is NOT removed from public view and consideration as a result, because there are a number of points that can be expressly shared with the community in light of this episode, and it is important that such points become part and parcel of our community development trajectory for the ongoing benefit of the wider communities that we concurrently serve as a whole, if nothing else.
so, on a less formal note without prejudice to the above, and in not so many words: you chaps may find it easier to get passed your perceived impasse if you begin your inquiries from the heartfelt appreciation that there has been no artificial manipulation of the variables involved, and the phenomena at hand (which has been consistently labelled “innovation precipitation” rather than tag cloud) has arisen as a naturally occuring artificat of our present elgg platform coupled with community members’ (and general public) interactions with the same.
for example, the use of the keyword “transformational flow” may be regarded as far from esoteric. its relevance to our community can be easily ascertained by typing in the same keyword as a standard google search term on the world wide web. doing so will lead you to extensive documentation relating to how the term is currently being used by the Office of Government Commerce’s Managing Successful Programmes best practice guidance. in fact, “MSP transformational flow” is listed as one of the three core concepts framing the entire model for the revised 2007 edition. the keyword “benefit realisation” stems from the same set of practices that are currently governing both how the U&I programme is becoming evaluated, and how the same may become better evaluable in light of our own specialist use cases in the context of web 2.0 and open source ethos informed technologies.
similarly, each of the keywords [...] in question have been authored to act as, inter alia, scholarly points of search and retrieval that lead primarily to richer content being stored within this here elgg digital repository, coupled with additional sources of emerging and related information being held elsewhere.
now, by way of seeking to creatively move on from here, an aporia green “easter elgg hunt” will be openly initiated to make this dynamic aspect of our community development more obviously visible to all members and general public alike. this aporia work is hereby offered in the hope of our cross-culturally stepping together towards something more than just what has merely gone before: so here’s bidding you a happy [...]; and relax – we’re all in the same emerging boat at the end of the day – there is no other.
at any event, all rights are reserved generally, and all being well, weblog post consolidating aporia green’s easter elgg hunt, and its story so far, to follow shortly with keyword “easter elgg hunt” as original identifier for the record [...]
[...] caveat emptor: this is not a this-is-not-a-game, albeit this m(a)y be a cricket ball if and only if this is not a caper, nor about any particular denial of caper as such; (un)unfiction rules hereafter, for the time being at least, all rites reserved generally otherwise [...]
[...] please find attached Aporia Green FAQ to include as an appendix to your bid as discussed, coupled with the following form of words to appear somewhere under the heading of your intended bid work-package for evaluation/ethnography/dissemination:
“This work-package will be managed in collaboration with Aporia Green (see appendix X) which has been emerging as a community-driven initiative within the [...] Programme’s [...] Community, complementary to the [...] Project Team (Support 1) and the [...] Team (Support 2) ongoing activities”
then simply allocate the amount you think is reasonable to cover this work package as a proportion of your overall budget. depending on take up across successful (and almost successful projects), the amounts allocated by individual project bids will contribute to Aporia Green’s pooled resources as a whole which, all being well, should extend to recruiting of specialist ethnographers across projects who would otherwise not be available piecemeal.
hope this keeps bid writing simple – and relatively homogenous for the bid markers over the coming period – this message is being blind copied to 7 individual projects, 5 from the emerge community and 2 without as far as I am aware. however, if you know of any other bids that may be interested in taking up this option with us, please feel free to pass this open invitation to them also [...]
[...] for the record, dear [...], people throughout the community need to know a couple of things arising out of this post and ensuing commentary – so here goes telling it (online) as it is.
first, for the avoidance of doubt, please take this response by way of notice that this set of posts is being flagged as both defamatory and offensive to the community member being wrongfully accused of artificially inflating the hit count relating to the tag cloud instances in question.
in this sense, am suggesting that both the programme manager and the project director (not to name and shame) consult their respective line managers as to how best to offer official redress – the chain of command may also wish to consult [...] Legal on the matters arising, particularly with regard to the careful phrasing of this here comment which is being posted publicly in formal response to said accusations.
additionally, the chain of command may wish to consult [...] on related risk management matters arising out of having procured and deployed elgg open source software thus far. for example, the attempted reverse-engineering of elgg specific algorithms may be in breach of existing software licensing agreements – access to source code does not usually extend to potential abuse of author/developers’ moral rights.
notwithstanding, it is important that this set of posts is NOT removed from public view and consideration as a result, because there are a number of points that can be expressly shared with the community in light of this episode, and it is important that such points become part and parcel of our community development trajectory for the ongoing benefit of the wider communities that we concurrently serve as a whole, if nothing else.
so, on a less formal note without prejudice to the above, and in not so many words: you chaps may find it easier to get passed your perceived impasse if you begin your inquiries from the heartfelt appreciation that there has been no artificial manipulation of the variables involved, and the phenomena at hand (which has been consistently labelled “innovation precipitation” rather than tag cloud) has arisen as a naturally occuring artificat of our present elgg platform coupled with community members’ (and general public) interactions with the same.
for example, the use of the keyword “transformational flow” may be regarded as far from esoteric. its relevance to our community can be easily ascertained by typing in the same keyword as a standard google search term on the world wide web. doing so will lead you to extensive documentation relating to how the term is currently being used by the Office of Government Commerce’s Managing Successful Programmes best practice guidance. in fact, “MSP transformational flow” is listed as one of the three core concepts framing the entire model for the revised 2007 edition. the keyword “benefit realisation” stems from the same set of practices that are currently governing both how the U&I programme is becoming evaluated, and how the same may become better evaluable in light of our own specialist use cases in the context of web 2.0 and open source ethos informed technologies.
similarly, each of the keywords [...] in question have been authored to act as, inter alia, scholarly points of search and retrieval that lead primarily to richer content being stored within this here elgg digital repository, coupled with additional sources of emerging and related information being held elsewhere.
now, by way of seeking to creatively move on from here, an aporia green “easter elgg hunt” will be openly initiated to make this dynamic aspect of our community development more obviously visible to all members and general public alike. this aporia work is hereby offered in the hope of our cross-culturally stepping together towards something more than just what has merely gone before: so here’s bidding you a happy [...]; and relax – we’re all in the same emerging boat at the end of the day – there is no other.
at any event, all rights are reserved generally, and all being well, weblog post consolidating aporia green’s easter elgg hunt, and its story so far, to follow shortly with keyword “easter elgg hunt” as original identifier for the record [...]