[Foundation-l] Guidelines for the use of iframes?

[MZMcBride]

MZMcBride wrote:
> Indeed. I've commented out the iframe for now while discussion continues.
> Once there's a clearer understanding of the implications of using this code
> and whether this particular third-party's policy is compatible with
> Wikimedia's.
> 
> I say "compatible" as it's a passive read action of wikimediafoundation.org
> that will trigger data being sent to Jobvite. Adding a footer might be nice,
> but if the user doesn't consent to Jobvite's privacy policy, simply reading
> wikimediafoundation.org has already sent their data to the other server,
> correct? In my mind, that means a footer or additional warning text is
> insufficient.

Quick update on this. I blanked the page, but it's already been switched
over as the central repository for Wikimedia Foundation job listings, so
simply blanking wasn't an option. It's kind of obscure, but Jobvite does
allow direct links to individual job listings. I put together an index of
the current job openings and even added back some of the old styling:
<https://wikimediafoundation.org/w/index.php?oldid=79813>. It doesn't
auto-update and it doesn't have the same categorization, but for right now,
as a stop-gap measure, it'll work.

I think the ideal solution would be for
<http://hire.jobvite.com/Jobvite/Jobs.aspx?c=qSa9VfwQ> to have an RSS feed
so that outsiders can follow Wikimedia job postings and the content can be
brought in to sites like wikimediafoundation.org using the same code that
powers the auto-updates of the Wikimedia blog to the home page of
wikimediafoundation.org. I'm not sure if this would support the same kind of
categorization scheme (perhaps multiple feeds would be needed or an
attribute could be specified?).

MZMcBride